Messaging and email

Slack Bot

Connect a Slack bot token and signing secret to start workflows from channel conversations, send messages and alerts, and upload files.

01 / Workflows

What you can automate.

The Slack Bot connection stores a Bot User OAuth token and signing secret. Runtara uses it for channel triggers and Slack actions such as sending messages and uploading files.

  1. Send workflow alerts or approval prompts to channels and users.
  2. Upload generated files into a Slack channel.
  3. Receive channel-triggered conversations verified by signing secret.

02 / Capabilities

What it covers.

The full reference, with connection types, is in the Slack Bot docs.

Capabilities

  • Send message
  • Block Kit and mrkdwn content
  • Upload file
  • Conversational channel triggers
  • Webhook signature verification

Data handled

  • Messages
  • Blocks
  • Files
  • Channel metadata

03 / Availability

In every edition.

Slack Bot is a standard integration, included in Cloud, Enterprise and the open-source engine. Compare plans

  • Open-source engineAGPL-3.0, run and operate it yourself.Included
  • CloudWe host and manage your instance.Included
  • EnterpriseYour cloud or on-premises, supported by our team.Included

04 / Questions

Common questions.

Is Slack Bot included in my plan?

Yes. Slack Bot is a standard integration, included in Cloud, Enterprise and the open-source engine.

How is it set up?

A connection stores the Slack Bot credentials once for your instance. Workflow steps that use it declare that connection, and the runtime denies anything else.

Can a person approve before anything is written?

Yes. A workflow holds an exception for approval and continues only after the person decides. The run keeps the source, the decision, who made it, and the response together.

More in Messaging and email

Put Slack Bot to work.

Start with a paid pilot of one real process. Our team builds and runs it, live in two weeks once access is in place.

Discuss your process

All product names, logos and brands are the property of their respective owners and are used here in good faith, only to identify the systems Runtara connects to. Their use does not imply any affiliation with, or endorsement or sponsorship by, those owners.