Short answer: Drop the "GetResponse → Create GetResponse 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 | Required | The email address. Used as the recipient or identifier depending on context. | |
Name name | string | Optional | Name |
Campaign ID campaignId | string | Required | The list/campaign to add the contact to |
{"email": "e.g. user@example.com","name": "{{trigger.name}}","campaignId": "{{trigger.campaignId}}"}
{"name": "John","email": "john@example.com","contactId": "contact123","createdOn": "2026-04-11T10:00:00Z"}
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.