APer-pair page

Connect Ashby to Slack in two minutes.

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

Connect Ashby to Slack — start free See reverse direction

Trigger app

Ashby as the trigger

Workflows fire when something happens in Ashby.

Ashby has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →

Both directions

Pick the way that fits your stack.

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

AAshby → Slack

When something happens in Ashby, do it in Slack.

0 Ashby triggers wired to 45 Slack actions.

ASlack → Ashby

Or fire it the other way around.

13 Slack triggers wired to 3 Ashby actions downstream.

See Slack → Ashby →

How it works

Connect Ashby and Slack in five steps.

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

1
Connect
Authorize Ashby and Slack
Open TinyCommand, authorize Ashby and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Ashby trigger
Drop the Ashby → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/ashby.event
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
Action
Add the Slack action
Drop the Slack → Add Reaction action below it. Map fields from the Ashby payload into the Slack inputs.
slack.add-reaction
5
Publish
Publish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Ashby + Slack.

How long does it take to connect Ashby and Slack on TinyCommand?

Under two minutes. Authorize Ashby and Slack once each, drop the Ashby trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Ashby ↔ Slack integration real-time?

Yes. Both Ashby and Slack 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 Ashby and Slack?

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 Slack.

What Ashby events can trigger a Slack workflow?

Use TinyCommand's universal Webhook trigger to receive Ashby events, then run any of the 45 Slack actions downstream.

Do I need a paid plan to use Ashby with Slack?

No. There's a free tier that covers most Ashby+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Slack → Ashby instead?

Build it the same way, in reverse. There's a dedicated /integrations/slack/with/ashby page with the reverse-direction triggers and actions.