Slack connector

The Slack connector makes Slack the place where a workflow tells people what happened and what needs their attention: it posts status and alerts, sends the right person the link to a decision waiting for them, and keeps channels and members in step with your other systems. Slack is a surface for notifications, not a system of record, so run state and decisions stay in Neblex.

• Uses the Slack Web API with 317 operations, signed in with a bot or user OAuth token from your Slack app
• Messages can use Block Kit, so a summary table or a link button renders natively rather than as plain text
• Approvals run in Neblex: a Wait for form step creates the task, and the flow posts its link to Slack so the approver can open it in one click
• AI agents can be Slack bots in their own right: the agent answers in threads, and Slack's signing secret is checked before it runs

The three jobs this connector is picked for most often, and what each one gets you.

• Put an approval in the flow. The run waits on a Neblex task with a due time and escalation, and the approver gets the link in Slack as well as by email.
• Route alerts with the context attached. A failed payment, a large deal, or an incident posts to the right channel with the record details and a link, not just a bare notification.
• Bring an assistant into Slack. An AI agent connected as a Slack bot answers questions in threads, using the tools and knowledge you gave it.

A real flow teams build on day one, with the actual step-level detail.

Discount over 20 percent waits for the deal desk before the quote is sent

A CPQ quote with a large discount pauses. Neblex sends the deal desk lead the approval task, posts the link to them in Slack, and the run continues only on approval.

1. 1
   Upstream: a quote reaches pending approval with discount_pct, deal_name, amount, and rep_email.
2. 2
   Resolve approver: a data table maps the rep's region to a deal desk owner's email. Find user by email returns their Slack user ID.
3. 3
   Request approval: a Wait for form step creates the approval task for that person with deal_name, amount, and discount_pct, a due time of 4 working hours, and an escalation flow.
4. 4
   Notify: post a Block Kit message to the approver with the deal summary and a button that opens the task.
5. 5
   Escalate: if the task passes its due time, the escalation flow posts to #deal-desk so someone else can pick it up.
6. 6
   Decide: on approve, set the quote to approved and let the send step run; on reject, set it to rejected and post the reason back to the rep in a thread.
7. 7
   Audit: the run records who decided and when, so the approval is provable later.

Common patterns other teams start from with this connector.

• Deal won alerts. A closed-won opportunity posts to the revenue channel with the amount, product, and a link, and threads the onboarding checklist underneath. (Sales)
• Failed payment triage. A failed subscription payment opens a task, posts to the billing channel with the customer and amount, and tracks the dunning steps in the thread. (Finance)
• Query result digest. A scheduled Snowflake query posts a formatted summary each morning with a link to the run. (Data)
• Escalation bridge. A high-priority ticket creates an incident channel, invites the on-call and the account team, and posts the ticket context and CRM account detail. (Support)

Slack is a messaging surface, so the objects are conversational. State that must persist belongs in Neblex or the system of record, not in a Slack message.

What you can work with

Channel, Direct message, Message, Thread, User, User group, File, Reaction, Reminder, Scheduled message, Canvas, Bookmark

Block Kit messages can carry buttons that link to a Neblex task, form, or app, where the person makes the decision.

The connection holds only the OAuth scopes you grant your Slack app in your workspace.

• OAuth scopes. Bot and user tokens are scoped per capability, for example chat:write, reactions:read, users:read.email. Grant only what a flow needs.
• Channel-limited install. The app can be added to specific channels only, so it cannot post to or read channels it was not invited to.
• Encrypted credentials. The token is stored encrypted and never shown again after you save the connection.
• Decisions recorded in Neblex. Each approval records who decided and when in the task history and the run, alongside every message the flow sent.

The shape of Slack's limits, as published at the time of writing. Verify the exact figures for your plan; they change without notice.

• Web API methods are rate tiered, with most read methods around 50 or more calls per minute, and message posting at roughly one message per second per channel
• Posting is a POST call, so turn on Retry on failure or an idempotency key for steps that must survive a rate limit
• A message carries up to 50 Block Kit blocks
• File uploads are capped at 1 GB, and message text at 40,000 characters, with 3,000 the practical limit for readability