Start free
APer-pair page

Connect Slack to Ashby in two minutes.

Real-time triggers from Slack, ready-made actions in Ashby. Filter, transform, and route without writing a line of code.

Connect Slack to Ashby — start free See reverse direction
Trigger app
Slack as the trigger

Workflows fire when something happens in Slack.

See all 13 triggers →
A
Action app
Ashby as the action

Workflows do something in Ashby, instantly.

Connect Slack to Ashby — start free
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

ASlack → Ashby

When something happens in Slack, do it in Ashby.

13 Slack triggers wired to 3 Ashby actions. Most-used pairing: App Home Opened → Create Candidate.

AAshby → Slack

Or fire it the other way around.

0 Ashby triggers wired to 45 Slack actions downstream.

  • Use any trigger in the catalog as the upstream.
See Ashby → Slack →
Popular pairings

Common Slack → Ashby workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 39 combinations
A
When app home opened in Slack, create candidate in Ashby.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

A
When app home opened in Slack, list candidates in Ashby.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

A
When app home opened in Slack, list jobs in Ashby.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

A
When app mentioned in Slack, create candidate in Ashby.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

A
When app mentioned in Slack, list candidates in Ashby.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

A
When app mentioned in Slack, list jobs in Ashby.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

A
When new channel in Slack, create candidate in Ashby.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

A
When new channel in Slack, list candidates in Ashby.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

A
When new channel in Slack, list jobs in Ashby.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

How it works

Connect Slack and Ashby in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Slack and Ashby

    Open TinyCommand, authorize Slack and Ashby once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Slack trigger

    Drop the Slack → App Home Opened trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/slack.trigger-app-home-opened
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Ashby action

    Drop the Ashby → Create Candidate action below it. Map fields from the Slack payload into the Ashby inputs.

    ashby.create-candidate
  5. 5
    Publish
    Publish and forget

    Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Slack + Ashby.

How long does it take to connect Slack and Ashby on TinyCommand?
Under two minutes. Authorize Slack and Ashby once each, drop the Slack trigger and Ashby action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Slack ↔ Ashby integration real-time?
Yes. Both Slack and Ashby expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Slack and Ashby?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Ashby.
What Slack events can trigger a Ashby workflow?
Any of the 13 Slack triggers, including "App Home Opened". Each fires in real time when the matching event happens in Slack.
Do I need a paid plan to use Slack with Ashby?
No. Both integrations come on every plan, including Free, which includes 1,000 credits a month with no credit card. Each workflow step uses 1 credit, and paid plans include more credits and team seats when you need them.
What if I want Ashby → Slack instead?
Build it the same way, in reverse. There's a dedicated /integrations/ashby/with/slack page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Slack.

+
Slack + Gmail
Email
+
Slack + Google Sheets
Spreadsheets & Databases
+
Slack + HubSpot
CRM & Sales
+
Slack + Stripe
Payments
+
Slack + Notion
Productivity
+
Slack + Airtable
Spreadsheets & Databases
Connect Slack to Ashby — start free