Real-time triggers from Aircall, ready-made actions in HubSpot. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Aircall.
Pair pages are mirrored. Each direction gets its own dedicated page.
3 Aircall triggers wired to 23 HubSpot actions. Most-used pairing: Call Created → Create Company.
18 HubSpot triggers wired to 6 Aircall actions downstream.
See HubSpot → Aircall →Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires the moment Aircall creates a call record — typically at call answer or right after voicemail drop. Payload includes the direction (inbound/outbound), the from/to numbers, the assigned user, and the associated contact if Aircall matched the number. The hook for "log every inbound call to the CRM" sync workflows.
Fires the moment Aircall creates a call record — typically at call answer or right after voicemail drop. Payload includes the direction (inbound/outbound), the from/to numbers, the assigned user, and the associated contact if Aircall matched the number. The hook for "log every inbound call to the CRM" sync workflows.
Fires the moment Aircall creates a call record — typically at call answer or right after voicemail drop. Payload includes the direction (inbound/outbound), the from/to numbers, the assigned user, and the associated contact if Aircall matched the number. The hook for "log every inbound call to the CRM" sync workflows.
Fires the moment Aircall creates a call record — typically at call answer or right after voicemail drop. Payload includes the direction (inbound/outbound), the from/to numbers, the assigned user, and the associated contact if Aircall matched the number. The hook for "log every inbound call to the CRM" sync workflows.
Fires once a call completes (either party hangs up). Payload includes duration, final recording URL if recording was on, and the disposition (answered, missed, voicemail). The standard hook for post-call workflows — generate the AI summary, log to CRM, route follow-up tasks based on disposition.
Fires once a call completes (either party hangs up). Payload includes duration, final recording URL if recording was on, and the disposition (answered, missed, voicemail). The standard hook for post-call workflows — generate the AI summary, log to CRM, route follow-up tasks based on disposition.
Fires once a call completes (either party hangs up). Payload includes duration, final recording URL if recording was on, and the disposition (answered, missed, voicemail). The standard hook for post-call workflows — generate the AI summary, log to CRM, route follow-up tasks based on disposition.
Fires once a call completes (either party hangs up). Payload includes duration, final recording URL if recording was on, and the disposition (answered, missed, voicemail). The standard hook for post-call workflows — generate the AI summary, log to CRM, route follow-up tasks based on disposition.
Fires when a tag is added to a call — either by the agent after wrap-up or by an automation rule. Useful for "tag-based routing" workflows: a "demo-requested" tag fires a workflow to book the demo; a "support-issue" tag opens a ticket in the support tool.
No code, no glue, no half-day setup. Each step is one click.
Open TinyCommand, authorize Aircall and HubSpot once each. Both connections are available to every workflow on your account.
Drop the Aircall → Call Created 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 Aircall payload into the HubSpot inputs.
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.
