Resources · Make integration

Responder.live Make integrationAutomate Responder.live with Make.

Can Make keep your Responder.live subscriber base in order for you? The Responder.live Make integration gives you 11 modules: 1 trigger, 9 actions and 1 search. This page shows you how to link your account and build a first working scenario, step by step.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Responder.live Make integration do?

The Responder.live Make integration links your Responder.live account to Make, a no-code tool where you build a scenario, an automation made of modules chained one after the other. Each module is one brick: it watches your subscribers, adds one, updates one or organizes your lists, without a single line of code.

Sign-ups that land where they belong. A form in another app collects a new contact, and Add a New Subscriber drops that person into Responder.live. Nobody copies names by hand anymore.

A list that follows what happens. Watch for New or Updated Subscribers spots every change, then Remove Subscriber From a List or Make Inactive in a List adjusts where that contact sits. New campaign coming? Create a New List gives it its own audience, and Create a New Personal Field adds the detail you want to store on each contact before the first sign-up arrives.

Clean exits. When someone asks to leave, Unsubscribe from the Account handles it in one module instead of a trip through the Responder.live settings.

Be aware of one thing: the Make documentation lists these modules by name only, with no description and no documented limit. What this page says about each one is read from its name, so test with Run once before trusting a module. If you are still choosing a tool, the n8n vs Make comparison lays out both options, the Make pricing page explains plans, and the Make training takes you further.

Connect

How do you connect Responder.live to Make?

  1. 01

    Copy your u_key in Responder.live

    Log in to Responder.live, click the gear icon in the upper left corner to open Settings, then open API. Switch on the u_key option and copy the value it shows. Keep it somewhere safe: it is the key Make will use.

  2. 02

    Add a module and open the connection

    In your Make scenario, add any Responder.live module and click Create a connection. A connection is your Responder.live account linked to Make once, then reused by every Responder.live module. The Connection name field is optional.

  3. 03

    Paste the token and save

    Paste the u_key value into the User Token field and click Save. If Make asks you to authenticate your account and confirm access, accept. The connection now appears in the module, ready to use.

First scenario

Your first scenario: add a subscriber from a form

GoalWhen a form in another app receives a sign-up, Make adds that person as a subscriber in Responder.live.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the form or sheet app where your sign-ups arrive, and choose its module that watches new entries.

  2. 02

    Add Add a New Subscriber

    Click the + on the right of that first module, search for Responder.live and choose Add a New Subscriber. Click Create a connection and paste your User Token, as shown above.

  3. 03

    Map the data

    Fill the module fields with data from the first module. Each sign-up travels as a bundle, one item passed from a module to the next, so you simply click the value you want from the list Make offers.

  4. 04

    Test with Run once

    Submit a test entry in your form, then click Run once. Make runs the scenario one time and shows the bundles each module received. Open Responder.live and check the new subscriber is there.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule: every 15 minutes by default, and never less than 15 minutes on the Free plan. Then switch the scenario on and let it run.

Triggers

What can start a Responder.live scenario?

1 module starts a scenario when something happens in Responder.live. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Responder.live as soon as it happens.

Responder.live1Watch for New or Updated Subscribers

Watch for New or Updated Subscribers

triggerIn the docs only

This trigger gives your scenario a starting point each time a subscriber appears or changes in Responder.live. Every contact it finds becomes a bundle that the next modules can act on, so you react to your audience instead of checking it yourself.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so it is not a live alert.
When to use it
when a change in Responder.live should be copied to a CRM, a sheet or a team message.
Watch out
an action in the same scenario that updates the subscriber can be picked up again on the next check.
Modules

What can Make do in Responder.live?

Responder.live gives you 10 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Subscribers

6 modules
Responder.live1

Search Subscriber

SearchIn the docs only

Before you change anything, Search Subscriber tells you whether a contact already exists in Responder.live. Like every search module in Make, it can return zero, one or several bundles, and each one flows to the next module.

When to use it
ahead of an update or a removal, to work on the right person.
Watch out
several results mean the next module runs once per result.
Responder.live2

Add a New Subscriber

ActionIn the docs only

You get a fresh contact in Responder.live without typing it in: Add a New Subscriber creates the subscriber from data another module passed along. It is the module most scenarios end with when leads come from outside.

When to use it
a form, a shop or a booking tool collects a new person and Responder.live should know about it.
Watch out
run Search Subscriber first if the same person may sign up twice.
Responder.live3

Remove Subscriber From a List

ActionIn the docs only

This module takes a contact out of one specific list and leaves the rest of the account alone. The subscriber stays in Responder.live; only that list membership goes away.

When to use it
someone finishes a program or buys the product a list was promoting, and should stop receiving that sequence.
Watch out
if the goal is a full exit, Unsubscribe from the Account is the module that fits, not this one.
Responder.live4

Make Inactive in a List

ActionIn the docs only

Make Inactive in a List pauses a contact inside a list rather than removing it, as its name indicates. From the name, the contact stays in the list, just no longer active.

When to use it
a customer puts an order on hold or a trial ends, and you may want them back later.
Watch out
the documentation does not describe how an inactive contact behaves, so test it with Run once.
Responder.live5

Update Subscriber

ActionIn the docs only

Update Subscriber keeps a contact's record current by rewriting the details you map from another app. The subscriber stays the same person in Responder.live, with fresher information.

When to use it
a customer changes something in your CRM or your shop and Responder.live should match.
Watch out
if the scenario starts with Watch for New or Updated Subscribers, this update can be caught by the trigger again and run the scenario another time.
Responder.live6

Delete Subscriber Tag

ActionIn the docs only

Tags label your contacts, and this module takes one off a subscriber when that label stops being true. Judging by its name, it only removes that tag, not the subscriber.

When to use it
a tag such as a lead status stops being true, for example after a purchase recorded in another app.
Watch out
nothing in the documentation says a deleted tag can be restored, so check the tag name before you switch the scenario on.

Other

4 modules
Responder.live7

Make an API Call

ActionIn the docs only

Make an API Call is the way out when the other modules stop short: it calls any endpoint of the Responder.live API with the connection you already have, so no second login is needed.

When to use it
you need an operation the listed modules do not cover.
Watch out
this one asks you to read the Responder.live API documentation yourself, since Make only sends the request you write.
Responder.live8

Unsubscribe from the Account

ActionIn the docs only

With one module, a contact leaves your whole Responder.live account instead of a single list. That is the answer to someone who says they want to hear nothing more from you.

When to use it
an opt-out request arrives through a form, a support tool or an email parser in another app.
Watch out
the effect is wider than Remove Subscriber From a List, so keep this module for real opt-outs and test it on a test contact first.
Responder.live9

Create a New List

ActionIn the docs only

A new list appears in Responder.live as soon as a scenario needs one, so a launch or an event gets its own audience without a trip to the settings. Following modules can then place subscribers inside it.

When to use it
a new product, webinar or event is created in another app and deserves a dedicated list.
Watch out
each run creates a list, so place it after the event that justifies it, not on every bundle.
Responder.live10

Create a New Personal Field

ActionIn the docs only

Personal fields store extra information on each subscriber, and this module adds a new one to your account. Once it exists, Update Subscriber and Add a New Subscriber have one more place to write data.

When to use it
a new form question or CRM property needs a matching spot in Responder.live.
Watch out
running it on every bundle would try to create the same field again, so keep it in a scenario that runs once.
Need help

Need help automating Responder.live with Make?

A person reads every message.

FAQ

Responder.live Make integration: common questions

01Is the Responder.live Make integration free?
On the Make side, yes: Responder.live is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Every module run counts as an operation, one execution of one module on one bundle, deducted from your plan. On the Responder.live side, the documentation requires a paid Responder.live account for the connection to work.
02What is needed to connect Responder.live to Make?
Three things: a Make account, a paid Responder.live account and your User Token. You find the token in Responder.live by clicking the gear icon for Settings, then API, then switching on the u_key option and copying its value. In Make, add a Responder.live module, click Create a connection, paste the value into the User Token field and click Save. If Make asks you to confirm access, accept and the connection is ready.
03Does the Responder.live trigger in Make react in real time?
No. Watch for New or Updated Subscribers is a scheduled trigger: Make checks Responder.live on the scenario's schedule, every 15 minutes by default. On the Free plan the shortest interval is 15 minutes, while paid plans go down to 1 minute. A new or changed subscriber therefore reaches your scenario at the next check, not the second it happens. If you need a faster reaction, shorten the schedule on a paid plan.
04What if a Responder.live module is missing in Make?
Use Make an API Call. This module calls any endpoint of the Responder.live API with the connection you already set up, so you can cover what the other modules leave out. You will need the Responder.live API documentation to know which request to send. The Make documentation gives no numbered limit for this app, so if a run fails, the Make troubleshooting guidance and the bundles shown by Run once are the first places to look.
05Should Responder.live be automated with Make or n8n?
It depends on the tool your team already uses. Make offers 11 ready-made Responder.live modules, including a scheduled trigger, and a visual editor where you test each step with Run once. The same app often has an n8n node too, so check which modules each tool offers for the actions you actually need. Pick the one that covers them. The n8n vs Make comparison on this site walks through both tools side by side if you want a closer look.