ActionGetResponseUpdated September 2026

How do I add a contact to GetResponse?

Short answer: You can create getresponse contact in GetResponse by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GetResponse Create GetResponse Contact action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create GetResponse Contact in GetResponse — start free All 2 GetResponse actions

Create GetResponse Contact in GetResponse — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Email 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

Sample request

{
  "email": "e.g. user@example.com",
  "name": "{{trigger.name}}",
  "campaignId": "{{trigger.campaignId}}"
}

Returns

{
  "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.

Triggered by

Apps that pair well as the trigger for Create GetResponse Contact.

Any of these apps can fire this action as part of a workflow.

Google Sheets → GetResponse

2 Google Sheets triggers

HubSpot → GetResponse

18 HubSpot triggers

FAQ

Questions about Create GetResponse Contact.

What does the Create GetResponse Contact action do in GetResponse?

Adds a contact to a GetResponse campaign with email, name, custom fields. The base hook for "form submission → push to GR campaign" sync workflows.

What inputs does Create GetResponse Contact require?

Required: Email, Campaign ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GetResponse returns an error?

The run history shows the failed step with its input and the error message GetResponse returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create GetResponse Contact support batch operations?

Run Create GetResponse Contact inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within GetResponse's rate limits.

More actions

Other GetResponse actions.

Action

List GetResponse Campaigns

Returns every campaign (GetResponse's term for list) with name and subscriber count. Useful for resolving campaign IDs at workflow setup.

Create GetResponse Contact in GetResponse — start free