Add Contact To List
autopilot.add_contact_to_list
ActionCRM & salesconnection required
Calls the Autopilot API with the connection's credentials.
Add an existing contact to a contact list. A contact already on the list comes back with not_modified set rather than as a failure.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Autopilot
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
list_id The Autopilot contact list to act on; list ids always start with 'contactlist_'. | string | Yes | — | — | contactlist_06444749-9C0F-4894-9A23-D6872F9B6EF8 |
contact The contact to act on: an Autopilot contact_id, or the contact's email address. | string | Yes | — | — | person_9EAF39E4-9AEC-4134-964A-D9D8D54162E7 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"contact": "person_9EAF39E4-9AEC-4134-964A-D9D8D54162E7",
"list_id": "contactlist_06444749-9C0F-4894-9A23-D6872F9B6EF8"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
list_id The contact list the change was applied to. | string | — |
contact The contact id or email address that was given. | string | — |
not_modified True when Autopilot reported the list was already correct. | boolean | — |
added True when this call is what put the contact on the list. | boolean | — |
{
"added": false,
"contact": "",
"list_id": "",
"not_modified": false
}See Add Contact To List run in a workflow.
In a technical demo we add the Autopilot connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.