Short answer: Drop the "ActiveCampaign → Update 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 |
|---|---|---|---|
Contact ID contact_id | string | Required | Contact ID. Example: 123 |
Email email | string | Optional | Email. e.g. "user@example.com" |
First Name firstName | string | Optional | Contact's first (given) name. |
Last Name lastName | string | Optional | Contact's last (family) name. |
Phone phone | string | Optional | Phone number in E.164 format (with country code, no spaces). |
{"contact_id": "e.g. 123","email": "user@example.com","firstName": "e.g. Jane","lastName": "e.g. Doe","phone": "e.g. +14155551234"}
{"contact": {"id": "123","email": "user@example.com"}}
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.