Resources · Zapier integration

GetResponse Zapier integrationAutomate GetResponse with Zapier.

The GetResponse Zapier integration gives you 6 triggers, 6 actions and 2 searches. Every trigger is polled: Zapier checks GetResponse on a timer set by your plan, so the free plan waits the longest. Here is what each step does and what it costs you.

See the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the GetResponse Zapier integration does for you

GetResponse is an email marketing suite: you keep contacts in lists, send newsletters and autoresponders, and build forms and landing pages to grow those lists. The GetResponse Zapier integration lets new contacts, lists, forms and campaigns start automations on Zapier, and lets Zapier add, update or remove contacts and draft newsletters for you.

Three results people usually build first. Contacts that land on the right list: New Contact starts the Zap and Create or Update Contact puts the person on a second list without creating a double. Lists that stay clean: Find Contact locates someone on a list and Remove Contact takes them off it, for example once they have bought. A newsletter drafted for every new list: New List fires when the team creates a list, and Create Newsletter prepares the message for it.

The thing to know before you build: all six GetResponse triggers are polling ones. None of them is instant, so on the free plan a new contact can wait up to the 15-minute check before your Zap reacts. If timing matters, the plan grid below is part of the decision.

What Zapier does not do here: no step deletes a list, a form or a landing page, and the five triggers about lists, forms, landing pages, newsletters and autoresponders react to creation only, not to edits. Contacts that joined before the Zap went live are never picked up.

The same app has a GetResponse n8n integration page and a GetResponse Make integration page if you are comparing tools.

Vocabulary

Zapier words, in plain English

Eight words come back on every Zapier page. Read them once here and the notes below read faster.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap, such as a new contact. Once the Zap is on, Zapier watches for that event.
Action
What the Zap does once it has started: the step that writes, sends or creates something for you, like a contact on a list.
Task
The unit Zapier bills you for: one action your Zap completes successfully. The number on your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app the moment it happens. GetResponse only polls.
Filter
A step that lets the Zap continue only when what arrived meets a condition you set, and stops it quietly the rest of the time.
Search step
A step that looks up something already in an app, such as a contact on a list, so the steps after it can use what it found.
Connection
Your GetResponse account linked to Zapier once, then reused by every step of every Zap that touches GetResponse.
Cost

What it really costs you

GetResponse is not a premium app, so it works from the free plan. The bill is counted in tasks, and checks never count.

  • Tasks on the free plan100 per month
  • Steps on the free plan2: one trigger, one action
  • Premium appNo, works on the free plan
  • Instant triggers0 of 6: all are polled

A trigger costs nothing, and Zapier checking GetResponse for new items costs nothing either, however often it looks. Each action that succeeds counts as one task; a failed one is not counted. A Zap that copies each new contact to a second list costs one task per contact. The free plan gives 100 tasks a month, two-step Zaps only, and a check every 15 minutes. A filter or a search step makes the Zap multi-step, which needs a paid plan. Since every trigger here is polled, the grid below decides how soon your Zaps react.

Connect

Connect your GetResponse account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box: type GetResponse and pick it. You need an existing GetResponse account before you start.

  2. 02

    Sign in to GetResponse

    Click Add connection. A new tab opens on GetResponse: sign in with the account that holds the lists you want to automate. Lists the account cannot reach will not show up in any dropdown.

  3. 03

    Grant access and reuse it

    Allow Zapier to use the account. The connection is saved, and every Zap you build with GetResponse reuses it, so the next one starts without signing in again.

First Zap

Your first Zap: webinar sign-ups moved to the nurture list

GoalEvery new contact on the webinar list is also put on the nurture list, without doubles, but only when they agreed to hear from you.

  1. 01

    Create the Zap

    Start building a new Zap. Pick GetResponse as the app that starts the Zap, New Contact as the event, your saved connection, and the webinar list in the List field.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent contacts of that list, so you map the next steps on a real person instead of an empty sample.

  3. 03

    Add the filter

    Click the plus icon and choose Filter. Pick the field that holds the consent answer, a text rule and the value. This step makes the Zap multi-step, so a paid plan is needed.

  4. 04

    Add Create or Update Contact

    Pick GetResponse with Create or Update Contact, choose the nurture list, and map the email from the trigger. An existing contact is updated rather than doubled.

  5. 05

    Test, then publish

    Test the action and check the nurture list in GetResponse. Then click Publish: from the next check on, every new webinar contact follows the same path.

Triggers

GetResponse triggers

6 events start a Zap when something happens in GetResponse. Zapier checks for them at the interval your plan allows.

1

New Autoresponder

Polling trigger

In Zapier“Triggers when a new autoresponder is created.”

Starts the Zap when someone creates a new autoresponder in GetResponse. It watches your marketing setup, not your contacts.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
several marketers build sequences and the team lead wants a log of every new one for review before it goes live.
Watch out
only creation counts; editing an existing autoresponder will not start the Zap.
2

New List

Polling trigger

In Zapier“Triggers when a new list is created.”

A new contact list in GetResponse sets this one off. It is the moment a new audience gets a home, before a single person has joined it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
each event or product launch gets its own list, and you want the follow-up material prepared as soon as the list exists.
Watch out
lists created before the Zap was published are never sent through it.
3

New Landing Page

Polling trigger

In Zapier“Triggers when a new landing page is created.”

This trigger reacts when a new landing page is created in GetResponse. It suits teams that publish pages often and want the rest of the company to know.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a growth team launches a page per campaign and the sales team needs to know which pages are live before calls start.
Watch out
the Zap hears about the page at the next check, not the second it is created.
4

New Newsletter

Polling trigger

In Zapier“Triggers when a new newsletter is created.”

Each newsletter created in GetResponse starts the Zap. It is the hook for anything that should follow a one-off email, as opposed to an automatic sequence.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a content team wants each newsletter logged in the editorial calendar without someone copying the subject line by hand.
Watch out
a Zap on this trigger that runs Create Newsletter creates one, which the next check picks up again, in a loop.
5

New Contact

Polling trigger

In Zapier“Triggers when a new contact is added to any list.”

A contact added to a list hands the person to your Zap, whatever brought them in. It is the trigger to use when people, not campaigns, are what you follow.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a B2B company wants every new subscriber on its demo list passed on to sales at the next check.
Watch out
the List field is required, so one Zap watches one list; three lists to follow mean three Zaps.
6

New Form

Polling trigger

In Zapier“Triggers when a new form is added.”

Fires when a new sign-up form is added in GetResponse. It tracks the forms themselves, not the people who fill them in, which is the job of New Contact.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
an agency builds forms for several clients in one account and wants a running list of what has been set up.
Watch out
forms that already existed before you published the Zap never pass through it.
Actions

GetResponse actions

GetResponse gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create or Update Contact

Action

In Zapier“Creates or updates a contact.”

Puts the person on the list you choose, and updates them instead if they are already there. One step covers both cases.

When to use it
the same people come back through different forms and you want one clean record per person.
Watch out
List and Email are both required, so the email has to reach the step from an earlier one.
2

Create Contact

Action

In Zapier“Creates a new contact.”

Adds a new person to one of your GetResponse lists, so sign-ups collected elsewhere start receiving your emails.

When to use it
a checkout or a booking tool collects emails and you want each buyer on your customer list.
Watch out
List and Email are required; if the person may already be there, Create or Update Contact is the safer choice.
3

Create Newsletter

Action

In Zapier“Creates a new newsletter.”

Prepares a newsletter in GetResponse with its name, subject, list and sender address. Two delivery options are on offer: Time Travel sends by each contact's time zone, Perfect Timing when they are most likely to open.

When to use it
a new list for an event should get its welcome newsletter without someone building it from scratch.
Watch out
Time Travel and Perfect Timing cannot be combined, so pick one.
4

Remove Contact

Action

In Zapier“Deletes a contact from a list.”

Takes a contact off a list for you. It is the step that keeps a prospect list from emailing people who already bought.

When to use it
a deal closes in your sales tool and the person should leave the prospect list at once.
Watch out
the Contact field is required; GetResponse suggests the + Add search step button to find them on the right list first.
5

Update Contact

Action

In Zapier“Updates a contact.”

Changes the details of a contact already in GetResponse, so information gathered in another tool reaches your email marketing.

When to use it
your CRM learns something new about a subscriber and your segments should reflect it.
Watch out
the Contact field is required, so a Find Contact step usually comes first to hand it over.
6

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced step that sends a raw request to GetResponse with your existing connection, for the jobs no ready-made action covers.

When to use it
someone on the team knows the GetResponse API and needs one call the list above does not offer.
Watch out
requests only reach GetResponse's own domains, and the required Stop on error choice decides whether a failure halts the Zap.
Searches

GetResponse searches

2 search steps look for data that already exists in GetResponse, so a later step can use it.

A search step finds something that already exists in GetResponse and hands it to the steps after it. In the editor, searches sit at the bottom of the action list under their own heading. Three settings decide what happens when the lookup does not go to plan.

1

Find List

Search

In Zapier“Finds an existing list.”

Looks up an existing list by its name, so a later step can use that list without you picking it by hand in the editor.

When to use it
the list to use depends on what came in, for instance the name of an event typed in a form.
Watch out
Name is required; how close the match must be is GetResponse's call, so copy the name exactly as it appears.
2

Find Contact

Search

In Zapier“Finds an existing contact.”

Finds a person on a given list from their email, and hands the record to the steps that follow. It is what Update Contact and Remove Contact usually need.

When to use it
before removing a buyer from the prospect list, to get the right record.
Watch out
both the list and the email are required, and the search only looks in the list you give it.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns a search into a find-or-create. GetResponse offers no such variant on Zapier, so the box does not show on these two searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first, which is the default, stop the Zap, or hand them all on.
When it breaks

When it breaks

Zapier attaches one getting-started article to GetResponse and no list of known issues. The cases below come from how polled Zaps behave around an email list.

With GetResponse, the first surprise is timing: everything is polled, so nothing happens the second a contact joins. The rest are classic Zap behaviours that hit lists especially hard, because lists grow in bulk and contacts move between them. When a run fails, our Zapier troubleshooting page is the place to start.

  • The Zap reacts later than expected

    All six triggers are polled. On the free plan Zapier checks every 15 minutes, so a contact can wait until the next check before anything happens.

  • Old contacts are never picked up

    A Zap only reacts to what happens after you publish it. Contacts already on the list stay out, and moving that backlog is a separate job.

  • A list that feeds its own Zap

    A Zap on New Contact that adds contacts to the very list it watches finds them again at the next check, and the task count drains fast.

  • A bulk import held back

    Importing a large file of contacts returns a huge batch at once, and Zapier's flood protection can hold those runs back instead of firing them all.

  • A search that stops the Zap

    If Find Contact or Find List comes back empty with the default setting, the Zap stops there and Update Contact or Remove Contact never runs.

  • Newsletter timing options clash

    Create Newsletter offers Time Travel and Perfect Timing, but they cannot be combined. Decide per newsletter which of the two you want.
Need help

Need help automating GetResponse with Zapier?

A person reads every message.

FAQ

GetResponse and Zapier: your questions

01Is the GetResponse Zapier integration free?
Yes, for two-step Zaps. GetResponse is not a premium app, so the free Zapier plan accepts it, with 100 tasks a month and Zaps of one trigger and one action. A Zap where New Contact feeds Create or Update Contact fits. Add a filter, a second action or a search such as Find Contact, and the Zap becomes multi-step, which needs a paid plan. On the free plan the six triggers are also checked every 15 minutes, so a new contact can wait that long.
02How many tasks does a GetResponse Zap use?
One task per successful action, nothing for the trigger and nothing for the checks. A Zap that copies each new contact to a second list costs one task per contact. A failed action is not counted. In a Zap with a search and two actions, each successful action counts on its own. The real risk is volume: a list that gains hundreds of contacts after an event spends hundreds of tasks if every one of them goes through.
03Is GetResponse on Zapier real-time?
No. All six GetResponse triggers are polling ones: Zapier checks GetResponse at an interval set by your plan, 15 minutes on Free, 2 on Professional and 1 on Team and Enterprise. None of them is instant, so even a paid plan leaves a short wait. On paid plans you can also change how often the check runs, and run one by hand from the editor when you are testing. If speed is critical, factor the plan into the decision.
04What does it take to connect GetResponse to Zapier?
A GetResponse account with the lists you want to use already created. In Zapier you open Apps, click + Add connection, pick GetResponse, sign in in the tab that opens and grant access. The connection is saved and every later Zap reuses it. Most steps ask for a List, from New Contact to Create Newsletter, and they only offer lists that exist in the connected account. Create them in GetResponse before you build.
05How do you remove a GetResponse contact with Zapier?
With Remove Contact, fed by a search. The action needs a Contact, and GetResponse itself suggests the + Add search step button to find the person first. In practice, add Find Contact before it with the list and the email, then map what it found into Remove Contact. The contact leaves that list. Keep in mind that Find Contact only looks in the list you give it, so a person on another list comes back empty.
06What if the GetResponse operation you need is not on Zapier?
Then API Request (Beta) is the way in. It sends a raw request to GetResponse with the connection you already have, which reaches parts of the API the ready-made steps skip. It is an advanced step: you set the method and the address, requests only go to GetResponse's own domains, and the required Stop on error choice decides whether a failure halts the Zap. Without someone comfortable with APIs, stay with the listed steps.
07Zapier, Make or n8n for GetResponse?
Compare on criteria, not on a ranking. On Zapier, GetResponse offers six triggers, six actions and two searches, but every trigger is polled, so reaction time depends on your plan. You pay per successful action, and searches or filters need a paid plan. This site has a GetResponse page for Make and one for n8n, to set against your own needs. Weigh monthly contact volume, how fast you need to react, and who maintains the flows.
Same platform

Other docs you might need on this stack.

Browse all integrations