Real-time triggers from Autopilot, ready-made actions in HubSpot. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Autopilot.
Pair pages are mirrored. Each direction gets its own dedicated page.
2 Autopilot triggers wired to 23 HubSpot actions. Most-used pairing: Contact Added → Create Company.
18 HubSpot triggers wired to 2 Autopilot actions downstream.
See HubSpot → Autopilot →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.
No code, no glue, no half-day setup. Each step is one click.
Open TinyCommand, authorize Autopilot and HubSpot once each. Both connections are available to every workflow on your account.
Drop the Autopilot → Contact Added trigger onto the canvas. TinyCommand auto-registers the webhook.
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
Drop the HubSpot → Create Company action below it. Map fields from the Autopilot payload into the HubSpot inputs.
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.
