Short answer: Drop the "Constant Contact → 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 UUID |
Email email_address | string | Required | Email address (required by API even on update) |
First Name first_name | string | Optional | First Name |
Last Name last_name | string | Optional | Last Name |
Company company_name | string | Optional | Company name |
Job Title job_title | string | Optional | Job title |
Update Source update_source | options | Optional | Who initiated the update |
{"contact_id": "06d4ca6a-3122-11ee-a32f-fa163e56c9b0","email_address": "user@example.com","first_name": "John","last_name": "Doe","company_name": "Acme Inc"}
{"last_name": "Doe","contact_id": "06d4ca6a-3122-11ee-a32f-fa163e56c9b0","first_name": "John","updated_at": "2026-04-11T10:00:00Z","email_address": {"address": "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.