Resources · Make integration

GetResponse Make integrationAutomate GetResponse with Make.

Your leads come from everywhere, your emails live in GetResponse. The GetResponse Make integration closes that gap with 24 modules, 3 of them triggers. This guide shows how to connect your account, build a first scenario and pick the right module.

Try the GetResponse integration on MakeSee the 24 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the GetResponse Make integration do for you?

The GetResponse Make integration lets Make read and change your GetResponse account for you: contacts, newsletters, campaigns and tags. You build a scenario (the automation itself, a chain of small bricks called modules) and Make runs it in the background, so data moves between GetResponse and your other tools without copy and paste.

Every lead lands in your audience. A form, a checkout or a booking tool collects a person; Create a Contact adds them to GetResponse, and List Contacts checks first whether they are already there. Nobody exports a CSV again.

Newsletters leave on a real signal. Your team writes the draft in GetResponse as usual. Send a Newsletter fires it when something happens elsewhere, and Cancel a Newsletter Sending pulls it back into a draft if the offer changes at the last moment.

New campaigns come with their paperwork. Watch Campaigns spots a campaign created in GetResponse, and the scenario opens the matching task or folder in your project tool, so the setup around it is never forgotten.

Two honest limits. All three triggers are scheduled: Make checks GetResponse at intervals, it is never told the instant something happens. And the documentation gives no numeric limit for the app. When a task has no module of its own, Make an API Call covers it with the same connection. If you are new to the editor, the Make training walks you through the basics.

The same app also has a node on n8n, covered in the GetResponse n8n integration guide. Weighing both tools? The n8n vs Make comparison lays out the criteria.

Connect

How do you connect GetResponse to Make?

  1. 01

    Add a GetResponse module

    Log in to Make, open a scenario and add any module from the GetResponse app. The connection (your GetResponse account linked to Make once, then reused by every GetResponse module) is set up from inside that module.

  2. 02

    Name the connection

    Click Add next to the Connection field. In Connection name, type something you will recognize later, like the account or brand it belongs to, then click Save.

  3. 03

    Approve the access

    If you were not already logged in to GetResponse, a window asks for your GetResponse credentials: fill them in and click Log in. Then confirm the access by clicking Yes, and the connection appears in the module.

First scenario

Your first scenario: new leads straight into GetResponse

GoalWhen a new lead shows up in another app, Make creates the contact in GetResponse.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. This first module is where the lead comes from: your form tool, your shop or your booking app.

  2. 02

    Set up the source

    Search that app by name, pick its module for new entries and connect your account. Once the connection exists, Make lists the forms or objects it can read, so you choose instead of typing.

  3. 03

    Add Create a Contact

    Click the + on the right of the first module, search GetResponse and choose Create a Contact. Pick your GetResponse connection, or create it as shown above.

  4. 04

    Map the lead's data

    Fill the fields Make shows for the contact by clicking into each one and picking the matching value from the first module. Each bundle (one lead passing from module to module) becomes one contact.

  5. 05

    Test with Run once

    Submit a test entry in your source app, then click Run once. Make runs the scenario one time and shows the bundle each module received. Check the new contact in GetResponse.

  6. 06

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and the Free plan cannot go shorter. Keep it or adjust it, then switch the scenario on.

Triggers

Which GetResponse events can start a scenario?

3 modules start a scenario when something happens in GetResponse. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by GetResponse as soon as it happens.

GetResponse1Watch Newsletters

Watch Newsletters

Scheduled trigger

In Make“Triggers when a new newsletter has been created.”

Starts your scenario each time a newsletter has just been created in GetResponse, and passes it on as a bundle so the next modules can read it, copy it or announce it.

How it fires
scheduled. Make checks GetResponse on the scenario's schedule, every 15 minutes by default, so a new newsletter reaches Make at the next check rather than the second it is saved.
When to use it
your sales or support team should see every newsletter before customers reply to it, or you keep a running log of newsletters in a sheet.
Watch out
it only reacts to newly created newsletters; a change to an existing one does not start the scenario.
GetResponse2Watch Contacts

Watch Contacts

Scheduled trigger

In Make“Triggers when a new contact has been created.”

Reacts to new contacts appearing in your GetResponse account, one bundle per new person, ready to be copied into the rest of your stack of tools.

How it fires
scheduled. Make asks GetResponse for news on the scenario's schedule, not at the moment someone subscribes. On the Free plan the shortest gap between two checks is 15 minutes; paid plans go down to 1 minute.
When to use it
a new subscriber should also exist in your CRM, or your sales team wants to hear about fresh signups where they already work.
Watch out
because of that polling gap, anything that has to feel immediate to the subscriber is better handled inside GetResponse itself.
GetResponse3Watch Campaigns

Watch Campaigns

Scheduled trigger

In Make“Triggers when a new campaign has been created.”

Kicks off the scenario when a new campaign is created in GetResponse, handing its details to the modules that follow.

How it fires
scheduled, like the two other GetResponse triggers. Make checks the app each time the scenario runs, on the clock you set on this first module.
When to use it
each new campaign should open a matching project, folder or page in the tools your team uses, so the work around the campaign starts at the same time as the campaign.
Watch out
none of the three GetResponse triggers is instant, so the scenario always waits for its next check before it reacts.
Modules

What else can Make do in GetResponse?

GetResponse gives you 21 modules in 5 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Newsletters

6 modules
GetResponse1

List Newsletters

Search

In Make“Lists all newsletters or searches for them by specified criteria.”

Pulls your GetResponse newsletters into the scenario, all of them or only those matching the criteria you set. Each newsletter comes out as its own bundle, so the next module runs once per newsletter.

When to use it
you want a recap of what went out, copied into a sheet or a report in another app.
Watch out
a broad search returns many bundles, and every one of them costs an operation further down.
GetResponse2

Get a Newsletter

Action

In Make“Returns a specified newsletter.”

Fetches one newsletter the scenario already knows and hands its details to the next module. Nothing changes in GetResponse: it is a read, nothing more.

When to use it
an earlier module, such as List Newsletters, pointed at a newsletter and you need its details before sharing it with the team or archiving it.
Watch out
map the newsletter from the earlier module rather than typing it by hand, or the scenario breaks the day it changes.
GetResponse3

Create a Newsletter

Action

In Make“Creates a new newsletter and puts it in a queue to send.”

Builds a new newsletter in GetResponse from data your scenario already holds, then places it in the sending queue. That second part matters: this module does not stop at a draft.

When to use it
content is written and approved in another tool, and nobody should have to rebuild it by hand in GetResponse.
Watch out
Run once really queues the newsletter, so test it with an audience made of your own team.
GetResponse4

Send a Newsletter

Action

In Make“Sends a newsletter draft.”

Takes a newsletter sitting as a draft in GetResponse and sends it. A person writes and checks the draft; the scenario only decides when it leaves.

When to use it
sending should wait for a signal elsewhere, like a product page going live or a manager approving the draft in your project tool.
Watch out
Run once sends for real, so keep a separate draft addressed to your team for your tests.
GetResponse5

Cancel a Newsletter Sending

Action

In Make“Cancels the sending of the newsletter and turns the newsletter into a draft.”

Stops a newsletter that is on its way out and turns it back into a draft you can edit. The content stays in GetResponse; only the sending is called off.

When to use it
a price, a date or a stock level changes in another app after the newsletter was queued, and the message is suddenly wrong.
Watch out
the newsletter comes back as a draft, so someone, or Send a Newsletter, has to send it again later.
GetResponse6

Delete a Newsletter

Action

In Make“Deletes a specified newsletter.”

Removes a newsletter from GetResponse. There is no undo from inside the scenario, so treat this step as final.

When to use it
drafts pile up from tests or abandoned ideas, and a cleanup decision taken in another tool should apply in GetResponse too.
Watch out
when it follows List Newsletters, click Run once and read the bundles before letting it act on the whole result.

Contacts

5 modules
GetResponse7

List Contacts

Search

In Make“Lists all contacts or searches for them by specified criteria.”

Searches your GetResponse contacts with the criteria you give and returns every match as a separate bundle. Zero matches is a valid answer too, and the scenario then has nothing to pass on.

When to use it
before creating someone, you want to know whether that person already sits in your account.
Watch out
several matches mean several runs of the next module, and as many operations on your plan.
GetResponse8

Get a Contact

Action

In Make“Returns a specified contact.”

Reads the record of one contact the scenario already points at and passes it forward, leaving GetResponse untouched.

When to use it
Watch Contacts just announced someone new and you need the rest of the record to fill your CRM or a sheet.
Watch out
choose it over List Contacts only when you already hold a precise contact; when you only have a clue, search first.
GetResponse9

Create a Contact

Action

In Make“Creates a new contact.”

Adds a person to GetResponse from data collected somewhere else: a form, a checkout, a signup in another tool. It is the door between your other apps and your email audience.

When to use it
new leads land in another app and should reach GetResponse without anyone exporting a file.
Watch out
if the same person can come back twice, place List Contacts before it so you update instead of duplicating.
GetResponse10

Update a Contact

Action

In Make“Updates a specified contact.”

Changes an existing contact in GetResponse with fresh data from another app, so your email side matches what the rest of the team knows.

When to use it
a customer upgrades, changes company or moves forward in your CRM, and the emails they receive should reflect it.
Watch out
it acts on one specified contact, so find that person first with List Contacts or pass them in from Watch Contacts.
GetResponse11

Delete a Contact

Action

In Make“Deletes a specified contact.”

Erases one contact from your GetResponse account. Once it runs, the scenario has no way to bring that person back.

When to use it
someone asks for their data to be removed through a form or a support ticket, and the request must reach GetResponse as well.
Watch out
feed it a contact coming from a search or a trigger, never a guess, and test it on a dummy contact first.

Campaigns

4 modules
GetResponse12

List Campaigns

Search

In Make“Lists all campaigns or searches for them by specified criteria.”

Returns your GetResponse campaigns, all of them or those matching your criteria, one bundle per campaign.

When to use it
a later module needs to know which campaign to work on, or you want an up to date inventory of campaigns in a spreadsheet.
Watch out
Make runs every following module once per campaign found, which adds up in operations on a busy account.
GetResponse13

Get a Campaign

Action

In Make“Returns a specified campaign.”

Hands the scenario the details of one campaign, without changing anything in GetResponse.

When to use it
Watch Campaigns has just spotted a new campaign and its details should go into a project board or a message to your team.
Watch out
it answers about one campaign only; to browse or filter, List Campaigns is the module you want.
GetResponse14

Create a Campaign

Action

In Make“Creates a new campaign.”

Opens a new campaign in GetResponse straight from your scenario, instead of someone setting it up by hand each time.

When to use it
every new product, event or client registered in another tool deserves its own campaign, named by one consistent rule.
Watch out
nothing stops a scenario from creating a second campaign for the same event, so check with List Campaigns first.
GetResponse15

Update a Campaign

Action

In Make“Updates a specified campaign.”

Edits a campaign that already exists in GetResponse, using values coming from earlier modules.

When to use it
an event gets renamed or a product line changes in your back office, and the campaign should keep up without a manual edit.
Watch out
the change lands on the campaign you specify, so feed it from Watch Campaigns, List Campaigns or Get a Campaign.

Tags

5 modules
GetResponse16

List Tags

Search

In Make“Lists all tags or searches for them by specified criteria.”

Lists the tags of your GetResponse account, or only those matching your criteria, each one as its own bundle.

When to use it
before adding a tag, you check whether it already exists so the account does not collect near duplicates.
Watch out
an empty result is normal when nothing matches, and the modules after it simply do not run.
GetResponse17

Get a Tag

Action

In Make“Returns a specified tag.”

Reads one tag and passes its details to the next module. A small brick, handy as a check before writing anywhere else.

When to use it
the scenario received a tag from List Tags and needs its current details before copying them into another app.
Watch out
anything that looks like browsing belongs to List Tags; Get a Tag wants one precise tag.
GetResponse18

Create a Tag

Action

In Make“Creates a new tag.”

Adds a new tag to GetResponse without anyone logging in to the app, so your labels follow the rest of your business.

When to use it
a new product, webinar or partner appears in another tool and you want a matching tag with the same wording.
Watch out
two runs can create the same tag twice, so search with List Tags beforehand.
GetResponse19

Update a Tag

Action

In Make“Updates a specified tag.”

Changes an existing tag in GetResponse with values from your scenario, which keeps your tags in line with how the team names things today.

When to use it
an offer changes name in your catalog and the related tag should follow the same wording.
Watch out
the module works on one specified tag, so pass it from List Tags or Get a Tag rather than typing it.
GetResponse20

Delete a Tag

Action

In Make“Deletes a specified tag.”

Removes a tag from your GetResponse account, and from the scenario's point of view that is final.

When to use it
an offer ends or a partnership closes, and its tag has nothing left to describe.
Watch out
before letting it run after List Tags, look at the returned bundles with Run once, since one loose criterion can remove far more tags than planned.

Other

1 module
GetResponse21

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the GetResponse API with the connection you already set up, for everything the listed modules do not cover.

When to use it
you need a GetResponse feature that has no dedicated module in Make, and you would rather not build a second connection for it.
Watch out
you write the request yourself here, so keep the GetResponse API documentation open next to the editor.
Need help

Need help automating GetResponse with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the GetResponse Make integration free?
Yes. GetResponse is a standard app in Make, so it works on the Free plan like the 3,000+ other standard apps. The Free plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Every module run counts as an operation on your monthly credits. Paid plans (Core, Pro, Teams, Enterprise) remove the cap on active scenarios and bring the interval down to 1 minute.
02What do you need to connect GetResponse to Make?
A Make account and a GetResponse account, nothing more: the documentation lists no other prerequisite. You add a GetResponse module, click Add next to the Connection field, give the connection a name and save it. If you are not logged in to GetResponse yet, Make asks for your credentials, then you confirm the access with Yes. That single connection is then reused by all 24 GetResponse modules, including Make an API Call.
03Do GetResponse triggers in Make fire in real time?
No. The 3 GetResponse triggers (Watch Newsletters, Watch Contacts and Watch Campaigns) are scheduled, and none is instant. Make checks GetResponse on the scenario's schedule, which is every 15 minutes by default and cannot go below 15 minutes on the Free plan. Paid plans let you check as often as every minute. If a delay of a few minutes is a problem for your use case, keep that part of the flow inside GetResponse and let Make handle the rest.
04What if the GetResponse module you need is missing?
Use Make an API Call. It calls any endpoint of the GetResponse API with the connection you already have, so you are not stuck with the 24 listed modules. The documentation gives no numeric limit for this app, so there is no documented ceiling to plan around on the Make side. Before writing a raw request, check whether a search module such as List Contacts or List Tags followed by an action already does the job; it is easier to maintain.
05Should you use Make or n8n for GetResponse?
It depends on the tool you already run. GetResponse has 24 modules in Make, with 3 scheduled triggers and a Make an API Call module for the rest, and it also has a node on n8n. Compare the two lists against the steps of your own workflow: the modules you need, the trigger you rely on, and who on the team will maintain the automation. If the team already builds in Make, starting there keeps everything in one editor.
Same platform

Other docs you might need on this stack.

Browse all integrations