GetResponse n8n integrationAutomate GetResponse with n8n.
The GetResponse n8n integration rests on two nodes. The GetResponse node exposes 5 operations on the Contact resource, and the GetResponse Trigger listens to 5 events spread over 5 families. Both read the same credential. Built for anyone wiring a mailing list into the rest of their workflows.
Verified Trustpilot reviews · AI, automation & growth agency
What does the GetResponse n8n integration actually do?
The GetResponse n8n integration pairs a node and a trigger. The node runs 5 operations on a single resource, Contact: create one, delete one, get one, get many, update one. The GetResponse Trigger registers a webhook, meaning a URL that GetResponse calls when something happens, and starts a workflow on any of 5 events. Both nodes read the same credential, so authentication gets set up once.
Start with the signup path. A visitor fills a form, GetResponse reports subscribe, and the trigger hands that event to the workflow. The rest is yours: append a row to Google Sheets for the weekly count, post a short line to Slack so the sales side sees the name before anyone answers. No copy and paste in the middle.
Second pattern, scoring. The click event says an email was clicked. Send it into contact.update, raise Scoring, add a value under Tag Names or IDs, and the contact record carries that signal into whatever segment you build next. The same shape works from survey, with the answers stored under Custom Fields.
Third, the export. contact.getAll with Return All switched on walks the pages of the API until the list is complete, instead of stopping at Limit. Those rows can land in a spreadsheet, feed a second tool such as Mautic, or simply answer how many contacts came in since a given date.
One detail worth knowing before you build: the trigger takes its list of events under Events, and List Names or IDs narrows what it watches to the lists you pick, chosen from the dropdown or passed as IDs through an expression, which is the small formula syntax n8n uses to pull a value from the previous step.
The node covers those five operations on the Contact resource. Anything outside them goes through the HTTP Request node, which calls any GetResponse API endpoint and reuses the same credential through predefined authentication, so there is no second login to manage.
Still choosing a platform? The n8n review lays out the trade offs and covers the expression syntax that fills every field above.
How do you connect GetResponse to n8n?
- 01
Grab the API key
Fastest route of the two supported methods. In GetResponse, open Integrations and API > API to view or generate an API Key. In n8n, open the Credentials menu, create a GetResponse credential, paste the key. A credential is the stored login n8n reuses, so this happens once and every later workflow picks it from a dropdown.
- 02
Or register an OAuth2 app
The second method needs two values from GetResponse: a Client ID and a Client Secret, which GetResponse calls the Client Secret Key, both generated when you register your application. Before saving, copy the OAuth Redirect URL shown in n8n and paste it into GetResponse as the Redirect URL. It has to be a URL on your own domain.
- 03
Attach it and activate
Open the GetResponse node or the GetResponse Trigger and pick the credential from its list. For the trigger, activating the workflow is what registers the webhook URL with GetResponse, so a trigger left inactive receives nothing. Node and trigger share the credential, which means one setup covers both sides of the integration.
What starts a workflow from GetResponse ?
GetResponse Trigger is the node that starts a workflow when something happens in GetResponse. It listens to 5 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your GetResponse account.
What you see in n8n
Every event, by family
One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.
click.*1click.click
open.*1open.open
subscribe.*1subscribe.subscribe
survey.*1survey.survey
unsubscribe.*1unsubscribe.unsubscribe
Configuration notes
01Set up the GetResponse Trigger
One trigger node covers all 5 events. You tick the ones you want and n8n registers a webhook, an address GetResponse calls the moment something happens, which is why events land in seconds with no polling loop to configure.
Key parameters
- Events: the list of events the workflow listens to. There is no catch-all value here, so every event you want has to be ticked.
- List Names or IDs: limits the watch to specific lists, picked from the dropdown or passed as IDs through an expression.
- Delete Current Subscription: a boolean inside the Options collection, described in the node as deleting the current subscription.
02Customer Subscribed and Customer Unsubscribed
These two events frame the life of a contact on a list. subscribe reports a customer subscribed to a list, unsubscribe reports one who left it. Ticking both keeps any copy of the list you hold elsewhere honest, since the two movements arrive through the same workflow.
Key parameters
- Events: tick both if the workflow keeps a mirror of the list somewhere else, or only one if you just want arrivals.
- List Names or IDs: useful here, since a company running several lists rarely wants the same downstream branch for all of them.
contact.get to read the record before deciding what to write. When the process also calls for removal, contact.delete takes it from there.03Email Opened and Email Clicked
Engagement events. open fires on an email opened, click on an email clicked. Both give the workflow a reason to act on a single contact rather than on the whole list, which is what makes them useful next to a CRM or a sales channel.
Key parameters
- Events:
clickalone stays quiet, whileopenwill be far chattier on a large list. Expected volume decides which one belongs in the workflow. - List Names or IDs: worth setting when only one campaign deserves this treatment, so the rest of the account stays out of the way.
contact.update to bump Scoring and write a value under Tag Names or IDs. Pair either event with a message to Telegram when a named account is the one engaging.04Survey Submitted
The survey event reports a survey submission. It sits apart from the other four: the other events react to an email or a list membership, this one reacts to something a person actively filled in, so the content behind it is usually worth more than the signal itself.
Key parameters
- Events: tick
surveyon its own for a dedicated workflow, since the branch that follows rarely resembles the subscribe branch. - List Names or IDs: scopes the trigger to the lists tied to the survey you care about, rather than every list in the account.
contact.create, with the answers stored under Custom Fields and a label under Tag Names or IDs, so the next person to open the record knows where it came from.What can the GetResponse node do?
The GetResponse node exposes 5 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Contact
5 operationsCreate a contact
contact.createWhat you see in n8n
Notes & use cases
Adds a new contact to GetResponse. No parameter on this operation is flagged as required in the node, so the fields you fill are the fields that reach the API.
Key parameters
- Email: the contact address, typed in or pulled from the item before it with
{{ $json.field }}. - Campaign Name or ID: picked from the dropdown, or given as an ID through an expression.
- Additional Fields: 7 optional fields, namely Name, Scoring, Tag Names or IDs, Custom Fields, Day Of Cycle, Note and IP Address.
Delete a contact
contact.deleteWhat you see in n8n
Notes & use cases
Removes a contact, identified by its ID rather than its email address. The Options collection holds 2 fields that change how the removal is recorded.
Key parameters
- Contact ID: required, the ID of the contact to delete. Empty, the node stops before it runs.
- Message ID: the ID of a message such as a newsletter, an autoresponder or an RSS newsletter. Passed here, the method simulates the unsubscribe process, as if the contact had clicked the unsubscribe link in that message.
- IP Address: passes the IP the contact unsubscribed from, and is used only if the Message ID was sent.
Get a contact
contact.getWhat you see in n8n
Notes & use cases
Reads one contact and returns its record, which the rest of the workflow can then branch on.
Key parameters
- Contact ID: required, the unique identifier for a particular contact.
- Fields: in the Options collection, a comma separated list of the fields to return. ID always comes back whatever you put there.
Get many contacts
contact.getAllWhat you see in n8n
Notes & use cases
Lists contacts. This is the operation that answers questions about a whole list rather than one person.
Key parameters
- Return All: on, n8n chains the API pages until every contact is back. Off, Limit caps how many come through.
- Options: 11 filters, including Campaign ID, Created On From, Created On To, Change On From, Change On To, Name, Origin with values such as
landing_page,webinarorsurvey, plus Sort By, Sort Order and Fields. - Exact Match: without it, matching runs as a standard like comparison, which the node warns may sometimes be slow.
Update a contact
contact.updateWhat you see in n8n
Notes & use cases
Changes the properties of an existing contact. Only what you put in Update Fields gets sent, which makes this the operation to reach for when a workflow needs to touch one attribute.
Key parameters
- Contact ID: required, the unique identifier for a particular contact.
- Update Fields: 9 fields, namely Email, Name, Campaign Name or ID, Tag Names or IDs, Custom Fields, Note, Day Of Cycle, IP Address and Scoring.
- Scoring: a number, and passing null removes the score from a contact.
Need help automating GetResponse with n8n?
A person reads every message.
