Skip to content
APer-pair page

Connect Autopilot to Slack in two minutes.

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

A
Trigger app
Autopilot as the trigger

Workflows fire when something happens in Autopilot.

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.

AAutopilotSlack

When something happens in Autopilot, do it in Slack.

2 Autopilot triggers wired to 45 Slack actions. Most-used pairing: Contact AddedRaw API Request.

ASlackAutopilot

Or fire it the other way around.

13 Slack triggers wired to 2 Autopilot actions downstream.

See SlackAutopilot
Popular pairings

Common Autopilot → Slack workflows.

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

Showing 8 of 90 combinations
A
When contact added in Autopilot, raw api request in Slack.

Fires when a new contact is added to Autopilot (now Ortto) from any source — manual create, CSV import, API write, or form submission. Payload includes the full contact with custom fields. The base hook for "new lead → fan out to slack/sheet/CRM" patterns.

A
When contact added in Autopilot, add reaction in Slack.

Fires when a new contact is added to Autopilot (now Ortto) from any source — manual create, CSV import, API write, or form submission. Payload includes the full contact with custom fields. The base hook for "new lead → fan out to slack/sheet/CRM" patterns.

A
When contact added in Autopilot, archive channel in Slack.

Fires when a new contact is added to Autopilot (now Ortto) from any source — manual create, CSV import, API write, or form submission. Payload includes the full contact with custom fields. The base hook for "new lead → fan out to slack/sheet/CRM" patterns.

A
When contact added in Autopilot, cancel scheduled message in Slack.

Fires when a new contact is added to Autopilot (now Ortto) from any source — manual create, CSV import, API write, or form submission. Payload includes the full contact with custom fields. The base hook for "new lead → fan out to slack/sheet/CRM" patterns.

A
When contact updated in Autopilot, raw api request in Slack.

Fires on any field change including custom-attribute writes and journey-state transitions. For specific change types (e.g., only when plan_tier becomes enterprise), inspect the previous_values vs current_values diff in the payload.

A
When contact updated in Autopilot, add reaction in Slack.

Fires on any field change including custom-attribute writes and journey-state transitions. For specific change types (e.g., only when plan_tier becomes enterprise), inspect the previous_values vs current_values diff in the payload.

A
When contact updated in Autopilot, archive channel in Slack.

Fires on any field change including custom-attribute writes and journey-state transitions. For specific change types (e.g., only when plan_tier becomes enterprise), inspect the previous_values vs current_values diff in the payload.

A
When contact updated in Autopilot, cancel scheduled message in Slack.

Fires on any field change including custom-attribute writes and journey-state transitions. For specific change types (e.g., only when plan_tier becomes enterprise), inspect the previous_values vs current_values diff in the payload.

How it works

Connect Autopilot and Slack in five steps.

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

  1. 1
    Connect
    Authorize Autopilot and Slack

    Open Tiny Command, authorize Autopilot and Slack once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Autopilot trigger

    Drop the Autopilot → Contact Added trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/autopilot.trigger-contact-added
  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 Slack action

    Drop the Slack → Raw API Request action below it. Map fields from the Autopilot payload into the Slack inputs.

    slack.api-request
  5. 5
    Publish
    Publish and forget

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

FAQ

Questions about Autopilot + Slack.

How long does it take to connect Autopilot and Slack on Tiny Command?
Under two minutes. Authorize Autopilot and Slack once each, drop the Autopilot trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Autopilot ↔ Slack integration real-time?
Yes. Both Autopilot 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 Autopilot 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 Autopilot events can trigger a Slack workflow?
Any of the 2 Autopilot triggers, including "Contact Added". Each fires in real time when the matching event happens in Autopilot.
Do I need a paid plan to use Autopilot with Slack?
No. There's a free tier that covers most Autopilot+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 → Autopilot instead?
Build it the same way, in reverse. There's a dedicated /integrations/slack/with/autopilot page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Autopilot.


Wire Autopilot to Slack in 2 minutes.

Free tier available. No credit card. No onboarding call.