Skip to content
OrqLabs
Türkçe'ye geç: ENTR

Messaging

Slack integration: team notifications and an internal AI assistant

Connect Slack once through its consent screen and every project in your organization can use the workspace. Workflows post reports and alerts to channels, and when the bot is mentioned or messaged directly, an AI assistant replies from your knowledge base.

Start freeStep-by-step setup guide
Connection type
OAuth
Scope
Per organization: all projects share one key
Inbound webhook
Yes, you get a webhook URL for incoming events
Capabilities
send messages, receive messages
Setup time
25 min

What it does in OrqLabs

The Slack integration does two jobs. First, team notifications: a weekly analytics summary, content waiting for approval or a campaign result is posted to the channel you choose with a Send message node in the workflow. Second, an internal assistant: DM the bot or @mention it in a channel, the message lands in the Inbox and the AI Chatbot replies from your knowledge base documents – in a thread under the original message.

Unlike the other messaging channels, Slack is connected organization-wide: you don't pick a project, and every project and workflow uses the workspace you connect once. The connection runs through Slack's OAuth consent screen; the bot scopes requested are listed on this page, and no user-level read access is requested.

Incoming events arrive through Slack's Events API and are verified with the Signing Secret. The bot only sees messages in public channels it has joined and DMs sent to it. To keep it from answering every channel message, use the keyword filter on the Message received trigger or build a flow that only replies to mentions and DMs.

What you can automate

  • Reports to a channel

    In a scheduled workflow, send the Report Writer's or Analytics Strategist's output to your team's channel with a Send message node (channel Slack, recipient the channel ID starting with C).

  • Slack assistant

    When the bot is mentioned or receives a DM, the AI Chatbot answers from your internal knowledge base – policies, product notes, FAQs – and posts the reply in the message thread.

  • Event alerts

    A workflow started by a platform event such as conversation.handoff, lead.replied or budget.warning forwards a short summary to the relevant Slack channel.

  • Managed in the Inbox

    Slack conversations appear in the Inbox like any other channel, so you can take over or correct the assistant's answers.

Agents that work with it

Nodes that use this integration

In the workflow editor these nodes run with your Slack account.

  • Message received

    Starts when a customer message arrives on a connected channel like WhatsApp or Telegram; e.g. so your chatbot answers automatically.

  • Send message

    Sends a message to one person on WhatsApp, Telegram, SMS and more, e.g. delivering a chatbot reply or an appointment reminder.

  • Hand off to human

    Passes the chat to someone on your team, silences the bot in that chat and alerts the team, e.g. when a customer complains or asks for a person.

Setup at a glance

  1. In OrqLabs, go to Integrations → Slack → Connect; there's no project to choose because the connection is organization-wide.

  2. Choose the right workspace on Slack's consent screen and click Allow; the card shows the workspace name.

  3. Invite the bot to the channels you'll post to with /invite @bot.

  4. For the assistant, paste the webhook URL from the card into Event Subscriptions → Request URL in your Slack app and wait for Verified.

  5. Save the bot events (app_mention, message.im, message.channels); if Slack asks you to reinstall, click Reauthorize in OrqLabs.

  6. Test by DMing the bot or typing @bot hello in a channel – the conversation should show up in the Inbox.

Read the full setup guide →

Requirements

  • Permission to install apps in the Slack workspace and the Owner or Admin role in OrqLabs.
  • The Slack app configured on the platform (the platform admin sets the Client ID, Client Secret and Signing Secret).
  • The bot invited to every channel it should post in (/invite @bot) – it can't post to channels it isn't a member of.
  • For the assistant, Event Subscriptions to app_mention, message.im and message.channels.

Requested permissions

  • chat:write
  • channels:read
  • channels:history
  • app_mentions:read
  • im:history
  • im:write

What you enter when connecting

  • Notification channel (optional)

Good to know

  • Slack is connected at organization level, not per project: all your projects share the same workspace connection.
  • The bot can't read private channels; only public channels it has joined and DMs come in.
  • Slack isn't a broadcast channel – use WhatsApp, email or SMS for customer campaigns.
  • If you skip the webhook step, outgoing messages still work but nothing from Slack reaches OrqLabs.

Frequently asked questions

Can I use Slack just for notifications?

Yes. If you skip the webhook step, no incoming messages are received, but your workflows can still post to channels the bot has been invited to.

Will the bot reply to every channel message?

It only sees messages in public channels it has joined. Filter out the ones you don't want answered with the keyword filter on the Message received trigger, or build a flow that only replies to mentions and DMs.

Does the Slack bot work in private channels?

If invited to a private channel, the bot can post there, but it can't read private channel messages.

Do I need a separate Slack connection per project?

No. Slack is connected organization-wide; the workspace you connect once is available to all your projects.

Get started with OrqLabs

Build your first workflow today

Start on the free plan: connect your accounts, pick a template and stay in control with approval steps. No credit card required.

Start freeExplore the product