Short answer: Drop the "Aircall → Create Contact" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
First Name firstName | string | Optional | Jane |
Last Name lastName | string | Optional | Doe |
Company companyName | string | Optional | Acme Inc |
Phone Numbers phoneNumbers | array | Optional | Array of {label, value} objects. e.g. [{"label":"Work","value":"+15551234567"}] |
Emails emails | array | Optional | Array of {label, value} objects. |
{"firstName": "Jane","lastName": "Doe","companyName": "Acme Inc","phoneNumbers": "{{trigger.phoneNumbers}}","emails": "{{trigger.emails}}"}
{"contact": {"id": 501,"last_name": "Doe","first_name": "Jane","company_name": "Acme Inc"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.