Short answer: Drop the "Constant Contact → 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 |
|---|---|---|---|
Email email_address | string | Required | Contact email address |
First Name first_name | string | Optional | First Name. e.g. "John" |
Last Name last_name | string | Optional | Last Name. e.g. "Doe" |
Company company_name | string | Optional | Company name |
Job Title job_title | string | Optional | Job title |
List IDs list_memberships | string | Required | Comma-separated list IDs to add the contact to (required by API) |
{"email_address": "user@example.com","first_name": "John","last_name": "Doe","company_name": "Acme Inc","job_title": "VP of Engineering"}
{"action": "created","contact_id": "06d4ca6a-3122-11ee-a32f-fa163e56c9b0"}
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.