EmailReal-timeUpdated May 2026

Autopilot

Autopilot (Ortto) contact events

Autopilot (now rebranded as Ortto) is the customer-journey automation platform that uses a visual canvas to design email + SMS + push flows triggered by user behaviour. Tiny Command surfaces two triggers (Contact Added — a new contact entered Autopilot, Contact Updated — any field change including custom attributes) plus two actions (List Contacts and Get Contact). The connection uses an Autopilot API key from Settings → API. The contact model is the centerpiece: every customer is a single contact record with first/last name, email, custom fields, and a list of journey participations. Contact Updated fires on any field change including custom-field writes — so workflows that need fine-grained reactions (e.g., "fire when the plan_tier field changes to enterprise") filter on the previous_values vs current_values diff. The Autopilot/Ortto rebrand happened in 2022 but most existing customers still use the autopilot.app domain; the API is API-version-stable across the rebrand.

Connect Autopilot See 2 triggers

2triggers

2actions

≈ 2 minto set up

Freetier · no card

Triggers

Workflows start when Autopilot does.

2 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven

Trigger live

When contact added

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.

See what it returns →

Trigger live

When contact updated

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.

See what it returns →

Actions

Do anything Autopilot can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Get Contact	Returns the contact by ID or email with all standard and custom fields plus current journey participations. Useful for enrichment workflows that need a snapshot of Autopilot state before downstream decisions.	1 fields	View →
List Contacts	Paginated contact list with filters by segment, journey, custom-field value. For sync workflows that mirror Autopilot into a warehouse, paginate with the recent-update filter to incrementally pull only touched records.	1 fields	View →

Recipes

Pre-built Autopilot workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Autopilot → Slack alerts

AI-triage every Autopilot event, ping the right channel only when it matters.

Autopilot → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Autopilot → Notion database

Turn Autopilot into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Autopilot once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Autopilot field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Autopilot integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Autopilot to Tiny Command?

Open the Tiny Command workflow builder, drop in a Autopilot node, and click Connect. Authorize Autopilot once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Autopilot triggers does Tiny Command support?

Tiny Command supports 2 real-time Autopilot triggers, including "Contact Added", "Contact Updated". Each trigger fires within seconds of the event happening in Autopilot.

What Autopilot actions can I run from a workflow?

2 Autopilot actions are available out of the box, covering email operations like "Get Contact". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Autopilot integration real-time?

Yes. Contact Added and every other Autopilot trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Autopilot rather than on a polling schedule.

Do I need to write code to use Autopilot with Tiny Command?

No. Every Autopilot trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Autopilot API endpoint directly.

How much does the Autopilot integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Autopilot integration itself has no per-app surcharge.