Skip to content
CodeBook

Talk to a workflow manager from Slack, Teams, Telegram or WhatsApp

Install each chat integration with the right bot credentials, sender identities and callback address, then verify a reply in the original conversation.

In Factory settings → Plugins → Talk to the manager, choose one of the four chat tiles. You need a workflow with an enabled manager and a workspace owner or admin to configure it. If a workflow is unavailable in the picker, assign its workflow manager first. Each connection belongs to one workflow, so name it for the team and environment. The manager acts with the access of the person who connected the channel; choose the destination and permitted audience accordingly. A manager reply is not a person’s approval of a merge.

Slack

  1. Create or select a Slack app for the intended workspace. Configure the bot scopes app_mentions:read, im:history and chat:write to read mentions and direct messages and post replies. Add users:read if you want names instead of Slack IDs. Install it in the workspace. Get the Bot User OAuth Token from OAuth & Permissions and the Signing Secret from Basic Information → App Credentials.
  2. In CodeBook select Slack, name it and choose a workflow. Paste both credentials, save, and copy the displayed Request URL.
  3. In the Slack app enable Event Subscriptions with that URL. Subscribe to the bot events app_mention and message.im. If you changed scopes, reinstall the Slack app. Invite it into the intended channel before mentioning it.
  4. Run Test; confirm Slack recognizes the expected workspace and bot. Mention the bot with a read-only request such as “What needs attention?” Confirm a manager reply in the Slack thread. If the token test passes but no message arrives, check URL verification, events, installation and channel membership. To replace saved Slack credentials, replace the connection in CodeBook and update Slack's Request URL.

Microsoft Teams

  1. Prepare an Azure Bot and its Microsoft Entra app registration. Record its Microsoft App ID, Tenant ID, and a Client secret. For the secret use its Value, not its ID. Get the Entra object IDs of the people permitted to talk to this workflow.
  2. In the Microsoft Teams tile choose the workflow and enter those values. Under Who may write, enter one permitted person's Entra object ID per line. Save and copy the Messaging endpoint.
  3. In the Azure Bot's configuration set that endpoint, then add the Microsoft Teams channel. Install the bot's Teams app in your organization.
  4. Run Test and send a message to the installed bot as a listed person in the configured tenant. The manager should answer in the conversation. If it does not, verify the tenant, the person's object ID, the endpoint and the expiry of the client secret. A person's email address is not their object ID.

Telegram

  1. Create a bot with @BotFather using /newbot. Keep its bot token and identify at least one user's numeric Telegram ID; a username or phone number is not a Telegram ID.
  2. In Telegram, name the connection, choose the workflow and paste the Bot token. Enter the permitted IDs under Who may write, one per line. Save. CodeBook registers the webhook with Telegram; there is no URL or signing secret to copy into Telegram.
  3. Click Test and check that Telegram recognizes the bot and its webhook points here. Have a listed user open a private chat with the bot, start it and send a question. An unlisted sender is told their ID so the owner can decide whether to add them.
  4. If the webhook points somewhere else, check that another application is not using the same bot. Save this connection again only when it should own the webhook.

WhatsApp

  1. Prepare a Meta app with WhatsApp Cloud API and a sending number. Obtain the Phone number ID (not the visible telephone number), an Access token authorized for that number, and the Meta App secret. A temporary access token will need replacing.
  2. In WhatsApp, name the connection, choose the workflow and enter those three values. List the permitted senders' telephone numbers, including country code, under Who may write. Save and copy the displayed callback URL and Verify token.
  3. In the Meta app's WhatsApp → Configuration, register the callback URL and verify token, and subscribe to the messages field. The generated verify token for registering the webhook is different from the access token used to send a reply.
  4. Run Test, then message the connected business number from a listed telephone number. Look for the reply in that WhatsApp conversation. Free-form replies are limited to the 24-hour window following the user's message. If a later update cannot be sent, have the user write again; do not assume a delayed notification was delivered.

For all four providers, distinguish a successful credential test from an actual conversation. Use a permitted test sender, start with a read-only question, and verify the reply before directing work from that channel.