Documentation

Slack

Send and receive Slack messages from a pipeline (Events API + chat.postMessage), in BYO mode.

Slack

The Slack integration connects your workspace to your pipelines, in both directions: receive messages (a Slack message triggers a pipeline) and send replies (an agent or a node posts in a channel or in a thread).

What you can do with it

  • Receive messages from a channel via the Events API and trigger a pipeline on them.
  • Post a message in a channel or as a reply in a thread.
  • List channels / users, read recent messages to give context to an agent.

Tools and nodes

  • Read tools: slack.list_channels, slack.list_users, slack.read_messages.
  • Write tool (with confirmation): slack.post_message.
  • slack_outbound node — send via chat.postMessage, reply in a thread, with an exactly-once guarantee.
  • slack_inbound receiver — Events API entry point, with native signature verification on the raw body, an anti-replay window, anti-loop (a message from the bot does not re-trigger itself) and event deduplication.

Connection (BYO)

  1. Administration → Integrations → Slack.
  2. Enter the bot token (xoxb-…) and the signing secret of your Slack app.
  3. Point your app's Events API URL to the pipeline's slack_inbound receiver.
  4. Token and secret are encrypted at rest and never re-exposed.

Slack is a strict BYO connector: you use your own Slack app, with no metering and no betool margin. Event signatures are verified on the raw body — a forged message is rejected.

Use cases

  • Team assistant — an agent answers questions posted in a channel using your knowledge base.
  • Actionable notifications — a pipeline posts an alert in a thread and receives the operator's reply to continue processing.