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.
Workflows fire when something happens in Autopilot.
- Contact AddedWebhook
- Contact UpdatedWebhook
Workflows do something in Slack, instantly.
- Raw API RequestAPI
- Add ReactionAPI
- Archive ChannelAPI
- Cancel Scheduled MessageAPI
- Create CanvasAPI
- Create ChannelAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Autopilot, do it in Slack.
2 Autopilot triggers wired to 45 Slack actions. Most-used pairing: Contact Added → Raw API Request.
Or fire it the other way around.
13 Slack triggers wired to 2 Autopilot actions downstream.
See Slack → Autopilot →Common Autopilot → Slack workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
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.
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.
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.
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.
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.
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.
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.
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.
Connect Autopilot and Slack in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Autopilot and Slack
Open TinyCommand, authorize Autopilot and Slack once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Autopilot trigger
Drop the Autopilot → Contact Added trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/autopilot.trigger-contact-added - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd 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 - 5PublishPublish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.
