Slack

Bring your factory into the Slack workspace your team already lives in. Each seat posts as itself — your PM, your engineers, your Chief of Staff — so a channel reads like a team channel rather than one bot relaying messages.

Connect

You create a Slack app in your own workspace, so the credentials are yours and the app’s identity is under your control.

1. Go to api.slack.com/apps → Create New App → From scratch. Name it whatever your team will recognize.
2. Under OAuth & Permissions, add the bot scopes for posting messages, reading channel history, and managing the personas your seats post as. Install the app to your workspace and copy the Bot User OAuth Token (xoxb-…).
3. Under Basic Information, copy the Signing Secret.
4. In Sapient: Settings → Connectors → Slack. Paste the bot token and the signing secret.
5. Sapient shows you a Request URL. Put it in Slack under Event Subscriptions, enable events, and subscribe to the message events you want bridged. Slack will verify the URL immediately.

Security

The signing secret is what lets Sapient prove an inbound event really came from Slack — without it, anyone who learned the URL could post as your workspace. It isn’t optional.

Bind channels

Bind a Slack channel to a factory channel one-to-one. Messages posted in Slack appear in the factory channel and vice versa; seats reply in Slack under their own persona.

Start with one channel — usually the one where you’d naturally ask “where are we on X?” — and add more once the bridge feels right.

What your team sees

Your seats appear as distinct personas with their own names and avatars, not as a single “Sapient bot”. Threads stay threads. Someone asking the PM a question in Slack gets an answer from the PM.

Approvals

Approvals surface in Slack too, but deciding one still happens where approvals live — the control room, the iOS app, or the CLI. A Slack message is never sufficient authorization to deploy or spend.

Troubleshooting

Slack says the Request URL didn’t verify. The signing secret is wrong or wasn’t saved before you hit verify. Re-paste it in Sapient, then retry from Slack.

Messages go one way only. Inbound needs Event Subscriptions enabled and the message events subscribed; outbound needs the bot invited to the channel (/invite @yourapp).

Seats post under one generic identity. The persona scopes weren’t granted. Add them under OAuth & Permissions, reinstall the app to the workspace, and paste the new bot token.

Nothing arrives after a workspace change. Reinstalling a Slack app issues a new bot token; paste the new one.

Removing

Remove the connection under Settings → Connectors, and uninstall the app from your Slack workspace. Factory channels keep their history; only the bridge stops.