Resources · Make integration

Respond.io Make integrationAutomate Respond.io with Make.

Every new contact, tag change or closed chat in Respond.io can start a Make scenario. The Respond.io Make integration offers 38 modules: 10 instant triggers, 22 actions and 6 searches. This guide takes support and sales teams from the connection to a first scenario that runs.

Try the Respond.io integration on MakeSee the 38 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Respond.io Make integration do for your team?

The Respond.io Make integration links your Respond.io workspace to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, acts or searches. Respond.io tells Make as soon as a contact, a message or a conversation changes, and the next modules handle the follow-up for you.

Route new leads without opening the inbox. Watch New Contact fires when someone first reaches your workspace. Add a Tag to a Contact labels them, and Assign or Unassign a Conversation hands the chat to the agent who owns that segment.

Keep your CRM and Respond.io in step. When a customer record changes in another tool, Create or Update a Contact writes it into Respond.io, creating the person when they are new and updating them otherwise. Contact Lifecycle then moves them to the stage your sales team expects.

Close the loop after a chat ends. Watch Conversation Closed starts a scenario the moment an agent wraps up. Get a Contact pulls the full record, so a module from another app can log the outcome where your managers look.

What the listed modules do not cover, Make an API Call reaches with the same connection. The connection itself needs a Respond.io account on the Growth Plan or above. Respond.io may also have an n8n node: the n8n vs Make comparison helps you pick, and the Make review covers the editor. When a run fails, start with Make troubleshooting.

Connect

How do you connect Respond.io to Make?

  1. 01

    Copy your API token from Respond.io

    In Respond.io, open Settings, then Integrations. Select Developer API, click Edit, then Add Access Token. Copy the token shown on screen and keep it ready for Make.

  2. 02

    Add a Respond.io module and create the connection

    In your scenario, add any Respond.io module and click Create a connection. A connection is your Respond.io account linked to Make once, then reused by every Respond.io module. On an instant trigger, click Create a webhook first.

  3. 03

    Name it and paste the token

    The Connection name field is optional, but a clear name helps when you link more than one workspace. Paste the token you copied, confirm, and Make can start reading your contacts, tags and conversations.

First scenario

Your first scenario: tag every new Respond.io contact

GoalWhen a new contact is created in Respond.io, Make adds your lead tag to that contact.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Search for Respond.io and pick Watch New Contact as the first module of the flow.

  2. 02

    Create the webhook and the connection

    Click Create a webhook, then Create a connection and paste your API token. The webhook is the line Respond.io uses to warn Make whenever a contact appears.

  3. 03

    Add the tag action

    Click the + on the right of the trigger and choose Add a Tag to a Contact. Map the contact coming from the first module, then type the tag your team gives to fresh leads.

  4. 04

    Test with Run once

    Click Run once, then create a test contact in Respond.io. Open the bubble above each module to read the bundles it received: the new contact first, then the tag request.

  5. 05

    Switch the scenario on

    Once the test contact shows its tag, switch the scenario on. Each new contact now costs 2 operations, one per module, and operations are what Make counts on your plan.

Triggers

Which Respond.io events can start a scenario?

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

Respond.io1Watch Contact Assignee Updated

Watch Contact Assignee Updated

Instant trigger

In Make“Triggers when the assignee of a Contact is updated.”

Starts your scenario whenever a contact gets a new assignee, so the handover between agents becomes something Make can act on. Routing rules stop living only inside the inbox.

How it fires
instant. Respond.io calls Make through a webhook as soon as the assignee changes.
When to use it
a lead moves from the bot to a human seller and your CRM should show the new owner too.
Watch out
a reassignment made by one of your own scenarios will most likely fire it too, so keep the two flows apart.
Respond.io2Watch Contact Lifecycle Updated

Watch Contact Lifecycle Updated

Instant trigger

In Make“Triggers when a contacts lifecycle is updated”

Tells Make when a contact moves to another lifecycle stage, which is how you turn a stage change in Respond.io into work in your other tools.

How it fires
instant. The stage change reaches Make by webhook the moment the new stage is saved.
When to use it
a prospect reaches the stage your team calls customer and billing should open an account for them.
Watch out
a stage set by Contact Lifecycle in another scenario also triggers this one, so map which scenario owns which stage.
Respond.io3Watch Contact Tag Updated

Watch Contact Tag Updated

Instant trigger

In Make“Triggers when Tag(s) are removed or added on a Contact.”

Reacts when tags are added to a contact or removed from it. A single tag can then steer what the rest of the scenario does.

How it fires
instant. Respond.io sends the tag change to Make through a webhook right away.
When to use it
agents tag a chat as a complaint and a manager should see it in their own tool without scanning the inbox.
Watch out
both adding and removing a tag fire it, so read the bundle from Run once to see what each case sends.
Respond.io4Watch Contact Updated

Watch Contact Updated

Instant trigger

In Make“Triggers when any contact fields of a contact are updated.”

Fires as soon as any contact field of a contact changes, which gives you the widest net on your contact data in Respond.io.

How it fires
instant. Every saved edit is pushed to Make by webhook when it happens.
When to use it
a customer corrects their email in a chat and your mailing tool should get the same address.
Watch out
any field edit starts a run, and each run spends operations. If only tags or the lifecycle matter to you, the narrower triggers above cost less.
Respond.io5Watch Conversation Closed

Watch Conversation Closed

Instant trigger

In Make“Triggers when a conversation is closed.”

Hands Make the conversation the moment an agent closes it, which is the natural point to record what happened and plan the next step.

How it fires
instant. Respond.io notifies Make through a webhook when the conversation is closed.
When to use it
after each support chat, a satisfaction survey or a summary line should go to the customer file in your helpdesk.
Watch out
pair it with List Closing Notes in a Workspace if you want the closing note labels your team uses.
Respond.io6Watch Conversation Opened

Watch Conversation Opened

Instant trigger

In Make“Triggers when a conversation is opened.”

Gives your scenario a start signal each time a conversation opens, so each new exchange can set work in motion elsewhere.

How it fires
instant. Make hears about the opening through a webhook as it happens.
When to use it
during a product launch, you want every opened chat logged in a spreadsheet so the team can see the load.
Watch out
a conversation opened by Open or Close a Conversation in another scenario is likely to fire it as well.
Respond.io7Watch New Comment

Watch New Comment

Instant trigger

In Make“Triggers when a new comment is posted to a conversation.”

Picks up each new comment posted to a conversation, so the notes agents leave for each other can travel beyond Respond.io.

How it fires
instant. Every posted comment is sent to Make by webhook straight away.
When to use it
an agent writes a comment asking for a refund check and the finance team should get it in their own channel.
Watch out
comments posted by Add a Comment will most likely count too, so a scenario that comments and listens to comments can feed itself.
Respond.io8Watch New Contact

Watch New Contact

Instant trigger

In Make“Triggers when new Contact is created.”

Brings every contact created in Respond.io into Make the first time they appear, the cleanest starting point for lead routing.

How it fires
instant. Respond.io warns Make through a webhook the moment the contact exists.
When to use it
a stranger messages your shop for the first time and they should land in your CRM with a source tag.
Watch out
the doc advises a delay before acting on a freshly created contact, since Respond.io needs processing time.
Respond.io9Watch New Incoming Message

Watch New Incoming Message

Instant trigger

In Make“Triggers when a message is received.”

Delivers each message your customers send into Make, which lets you react to what people write, not only to who they are.

How it fires
instant. Each received message is pushed to Make by webhook on arrival.
When to use it
you want a copy of every inbound request in your ticket tool, where your support lead tracks volumes.
Watch out
busy inboxes send many bundles, and each one spends operations on every module of the scenario.
Respond.io10Watch New Outgoing Message

Watch New Outgoing Message

Instant trigger

In Make“Triggers when a message is sent.”

Captures each message sent from your workspace, so you keep a trace of what your team and your bots told customers.

How it fires
instant. Respond.io hands every sent message to Make through a webhook as it leaves.
When to use it
a quote sent in chat should also be saved against the deal in your CRM.
Watch out
a message sent by Send Message from a scenario is, in all likelihood, outgoing too, so a scenario that listens here and replies can loop.
Modules

What can Make do in Respond.io?

Respond.io gives you 28 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Respond.io1

Add a Comment

Action

In Make“Adds a comment to a conversation.”

Posts a comment on a conversation, so the agent handling it sees information coming from your other tools right next to the chat.

When to use it
a payment fails in your billing app and the agent talking to that customer should know before answering.
Watch out
if another scenario listens with Watch New Comment, this comment starts it as well.
Respond.io2

Add a Tag to a Contact

Action

In Make“Adds a tag(s) to a contact.”

Puts one or more tags on a contact, which is the quickest way to sort people inside Respond.io from events that happen elsewhere.

When to use it
a form on your site is submitted and the matching contact should carry a campaign tag.
Watch out
this labels a contact; to create a tag for the whole workspace, use Add Space Tag.
Respond.io3

Add Space Tag

Action

In Make“Create a Tag for the workspace”

Creates a new tag at workspace level, ready to be used on any contact afterwards. It builds your tag list, it does not tag anyone.

When to use it
each new product line added in your catalog should get its own tag in Respond.io before agents need it.
Watch out
run it before Add a Tag to a Contact when the tag may not exist yet.
Respond.io4

Assign or Unassign a Conversation

Action

In Make“Updates the assignee of a conversation”

Sets or clears who handles a conversation, so Make can do the dispatching your supervisors would otherwise do by hand.

When to use it
a message mentions an existing order and should go to the agent who owns that account.
Watch out
Get a User or List Users in a Workspace gives you the right user to pick; Watch Contact Assignee Updated will react to the change.
Respond.io5

Contact Lifecycle

Action

In Make“Update lifecycle stage”

Moves a contact to a lifecycle stage, keeping your funnel in Respond.io aligned with what really happens in sales or billing.

When to use it
an invoice is paid in your accounting tool and the contact should switch to the customer stage.
Watch out
to take a contact out of every stage rather than change it, the right module is Remove Contact Lifecycle.
Respond.io6

Create a Contact

Action

In Make“Creates a Contact. Leave the contact field empty if you want to store an empty value. It is highly recommended to add a delay before executing a new action after creating a new contact, as processing time is required.”

Adds a brand new contact to your workspace from data collected anywhere else, so agents find the person ready when they write in.

When to use it
a signup lands in your app and you want the person in Respond.io before their first chat.
Watch out
the doc strongly advises a delay before any action on the new contact, because Respond.io needs processing time. Leaving a field empty stores an empty value.
Respond.io7

Create a Custom Field

Action

In Make“Creates a custom field.”

Adds a custom field to the workspace so contacts can hold data that the standard fields do not cover, such as a plan name or an account ID.

When to use it
you are setting up a new workspace from a scenario and want the same fields as your main one.
Watch out
List Custom Fields in a Workspace tells you what already exists, which avoids creating twins.
Respond.io8

Create or Update a Contact

Action

In Make“Creates or updates a Contact. Leave the contact field empty if you want to store an empty value or remain the existing value. It is highly recommended to add a delay before executing a new action after creating a new contact, as processing time is required.”

Creates the contact when they are new and updates them when they already exist, which spares you a search step before each write.

When to use it
your CRM syncs customers into Respond.io and you cannot tell in advance who is already there.
Watch out
an empty field keeps the existing value or stores an empty one, and the doc advises a delay before acting on a newly created contact.
Respond.io9

Delete a Contact

Action

In Make“Deletes a contact.”

Removes a contact from your workspace, which is how a deletion decided elsewhere reaches Respond.io without an agent doing it by hand.

When to use it
a customer asks to be erased and your privacy process runs from one central tool.
Watch out
a deletion cannot be taken back from Make, so test on a dummy contact with Run once first.
Respond.io10

Delete Space Tag

Action

In Make“Delete the workspace Tag”

Deletes a tag from the workspace list, handy when you keep tags tidy from a scenario instead of from the settings screen.

When to use it
a campaign ends and its tag should disappear so agents stop using it.
Watch out
this removes the tag for the workspace; to take a tag off one contact only, use Remove a Tag.
Respond.io11

Get a Contact

Action

In Make“Retrieves a contact by an identifier.”

Fetches one contact from an identifier and returns the full record, so later modules can use every field and not just what the trigger carried.

When to use it
a conversation closes and you need the customer's details for the follow-up in another app.
Watch out
it needs an identifier; if you only know a name or a detail, start with Search Contacts.
Respond.io12

Get a Custom Field

Action

In Make“Retrieves a specific custom field.”

Reads the definition of a single custom field, useful when a scenario must know how a field is set up before writing into it.

When to use it
a sync scenario checks that the field it relies on still exists before updating contacts.
Watch out
it returns the field itself, not a contact's value in it; that value comes with Get a Contact.
Respond.io13

Get a Message

Action

In Make“Finds a specific message by identifier.”

Retrieves one specific message from its identifier, so a scenario can work on the exact text of a message and not a summary of it.

When to use it
a comment points to a message and you want its full content copied into a ticket.
Watch out
without the message identifier this module has nothing to look up, so plan where the ID comes from.
Respond.io14

Get a User

Action

In Make“Finds a specific user by identifier.”

Looks up one user of your workspace from an identifier, which gives you the agent's details for a notification or a report.

When to use it
Watch Contact Assignee Updated tells you who took the contact and you want that agent's name in a message to the team.
Watch out
users are your team members, not your customers; contacts come from Get a Contact.
Respond.io15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call”

Calls any endpoint of the Respond.io API with the connection you already set up, so you are not stuck when a listed module stops short.

When to use it
you need something none of the other listed modules offers and the Respond.io API documentation describes it.
Watch out
you write the request yourself, so keep the Respond.io developer docs open while you fill it in.
Respond.io16

Open or Close a Conversation

Action

In Make“Updates the status of a conversation.”

Changes the status of a conversation to open or closed, which lets Make tidy the inbox based on what happens elsewhere.

When to use it
a ticket is solved in your helpdesk and the matching chat in Respond.io should close too.
Watch out
closing through this module fires Watch Conversation Closed in any scenario that listens to it.
Respond.io17

Remove a Tag

Action

In Make“Removes a tag(s) from a contact.”

Takes one or more tags off a contact, the reverse of Add a Tag to a Contact, so a label can follow the real state of a customer.

When to use it
a trial user upgrades and the trial tag should come off their contact.
Watch out
the tag stays in the workspace list; Delete Space Tag is the one that deletes it everywhere.
Respond.io18

Remove Contact Lifecycle

Action

In Make“Unassign contact lifecycle stage”

Clears the lifecycle stage of a contact, leaving them with no stage at all rather than moving them to another one.

When to use it
a contact was staged by mistake by an import and should go back to neutral until someone qualifies them.
Watch out
to move someone to a different stage, Contact Lifecycle does it in one step.
Respond.io19

Send a Message (Legacy)

Action

In Make“Sends a message to a Contact.”

Sends a message to a contact through the older version of the module, as the Legacy label in its name shows.

When to use it
an existing scenario already relies on it and works, so you have no reason to rebuild it yet.
Watch out
for a new scenario, pick Send Message instead, which does the same job without the Legacy label.
Respond.io20

Send Message

Action

In Make“Sends a message to a Contact.”

Sends a message to a contact from Make, so a confirmation, a reminder or an answer can go out without an agent typing it.

When to use it
a booking is confirmed in your calendar tool and the customer should get the details in the chat they started.
Watch out
this message counts as outgoing, so a scenario on Watch New Outgoing Message will see it.
Respond.io21

Update a Contact

Action

In Make“Updates Contact Field(s) of a Contact. Leave the contact field empty if you want to remain the existing value.”

Changes contact fields on an existing contact, so data corrected in another tool shows up in Respond.io for the agents.

When to use it
a customer changes their address in your shop and the Respond.io record should match.
Watch out
leave a field empty to keep its current value; if the contact may not exist, Create or Update a Contact is safer.
Respond.io22

Update Space Tag

Action

In Make“Update the workspace Tag”

Edits an existing workspace tag, so your tag list can follow changes decided in another tool without a trip to the settings.

When to use it
a product changes in your catalog and its Respond.io tag should change with it.
Watch out
this module edits and does not create; if the tag may not exist yet, go through Add Space Tag.
Respond.io23

List Channels in a Workspace

Search

In Make“Return all the channels of a workspace.”

Returns all the channels connected to your workspace, one bundle per channel, which helps when a scenario must pick where to send.

When to use it
you build a report of the channels your team answers on.
Watch out
as a search, it can return several bundles, and each following module runs once per bundle.
Respond.io24

List Closing Notes in a Workspace

Search

In Make“Return all the Closing Notes of a Workspace”

Gives back the closing notes defined in the workspace, the labels agents choose when they close a conversation.

When to use it
a scenario on Watch Conversation Closed should translate the closing reason into a readable label in your report.
Watch out
several notes mean several bundles, which multiplies the operations of the modules placed after it.
Respond.io25

List Contact Channels

Search

In Make“Find connected Channels of a Contact.”

Finds the channels a given contact is connected on, so you know where you can actually reach that person.

When to use it
before Send Message, you want to check which channel the customer uses to avoid sending into a void.
Watch out
a contact with no channel returns zero bundles, and the scenario stops there for that contact.
Respond.io26

List Custom Fields in a Workspace

Search

In Make“Return all the Custom Fields of a Workspace.”

Lists every custom field the workspace holds, a useful map when you sync data and must match fields between tools.

When to use it
you plan a CRM sync and want to check which fields Respond.io already offers before creating new ones.
Watch out
each field arrives as its own bundle, so place it where one run per field makes sense.
Respond.io27

List Users in a Workspace

Search

In Make“Return all the users of a Workspace.”

Returns all the users of your workspace, handy for dispatch logic that has to choose among the agents available.

When to use it
a scenario spreads new conversations across agents and needs the full team list first.
Watch out
to fetch one known user, Get a User is lighter than listing everyone.
Respond.io28

Search Contacts

Search

In Make“Return multiple Contacts that matches with the search condition.”

Finds the contacts matching a search condition and returns each one as a bundle, the tool of choice when you do not have an ID.

When to use it
an order arrives with a phone number and you want the matching contact before adding a comment.
Watch out
it can return zero, one or several contacts; plan for each case so a missing match does not break the run.
Need help

Need help automating Respond.io with Make?

A person reads every message.

FAQ

Respond.io and Make: frequent questions

01Is the Respond.io Make integration free?
Yes, on the Make side. Respond.io is a standard app, so its 38 modules work from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. The condition sits with Respond.io: the doc asks for an active Respond.io account on the Growth Plan or above, and that subscription is handled by Respond.io, not by Make.
02What is needed to connect Respond.io to Make?
An active Respond.io account on the Growth Plan or above, plus an API access token. You create the token in Respond.io under Settings, then Integrations, then Developer API, with Edit and Add Access Token, and you copy what appears on screen. In Make, add a Respond.io module, click Create a connection, optionally give the connection a name, and paste the token. For an instant trigger, click Create a webhook before the connection. The connection is then shared by every Respond.io module you add later.
03Do Respond.io triggers in Make fire instantly?
Yes. All 10 Respond.io triggers are instant: Respond.io calls Make through a webhook as soon as the event happens, whether it is a new contact, a tag change, a lifecycle update, an opened or closed conversation, a comment or a message. That is why the setup asks you to click Create a webhook before creating the connection. None of them relies on the 15 minute schedule that polling triggers use by default. Each event still spends operations on every module that runs, so busy triggers like incoming messages deserve a lean scenario.
04What if a Respond.io module is missing in Make?
Use Make an API Call. It is part of the 38 modules and can call any endpoint of the Respond.io API with the connection you already have, so you do not need a second setup. You write the request yourself from the Respond.io developer docs. Before that, check the 22 actions and 6 searches: several needs are covered by pairs such as Search Contacts followed by Update a Contact. The Make doc for this app also notes that its content is AI-generated from Respond.io documentation, so confirm important details with Respond.io.
05Make or n8n for Respond.io?
It depends on where your team already builds. In Make, Respond.io is a standard app with 38 modules, 10 instant triggers and Make an API Call, and it runs from the Free plan. The same app often has an n8n node as well, so if your automations already live in n8n, check what that node offers before splitting work across two tools. The useful criteria are the modules you need, the triggers available and the tool your team maintains. The comparison page linked above goes through both tools in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations