Resources · Make integration

Reply Agent Make integrationAutomate Reply Agent with Make.

Your Reply Agent contacts can update themselves while you work on something else. The Reply Agent Make integration gives you 9 modules: 1 trigger, 7 actions and 1 search. This page shows how to link your account, then walks you through a first working scenario.

Try the Reply Agent integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Reply Agent Make integration let you automate?

The Reply Agent Make integration links your Reply Agent account to Make, a visual tool where you chain apps together without code. The automation you build there is called a scenario: it reacts to new contacts in Reply Agent, then tags them, fills their custom fields or sends them a Smart Flow.

Sort every new contact on arrival. Watch New Contacts picks up the people who just landed in Reply Agent, and Apply a Tag labels them right away. Your support team opens a list that is already sorted instead of tagging by hand.

Keep contact data in sync with your other tools. When a deal closes in your CRM or a form comes in, Search Contacts by a Custom Field finds the matching person and Set a Custom Field writes the new value. Remove a Tag cleans up the label that no longer applies.

Start a conversation at the right moment. Send a Smart Flow launches one of the flows you prepared in Reply Agent, triggered by an event in another app rather than by someone remembering to do it.

Know the limits before you start. The Make documentation for Reply Agent is short: it lists the modules but gives no field details and no quotas, and it warns that its text was generated from the vendor docs and may contain mistakes. When a listed module is not enough, Make an API Call reaches the rest of the Reply Agent API with the same account link. To see how Make compares with its closest alternative, read n8n vs Make; to budget your usage, see Make pricing. If you would rather have the team build it, the Make agency page explains how we work.

Connect

How do you connect Reply Agent to Make?

  1. 01

    Generate your Reply Agent API key

    Log in to your Reply Agent workspace and open Settings. In the sidebar, click Connect, then API. If no key exists yet, click Generate Key, and copy the key shown on screen.

  2. 02

    Add a Reply Agent module in Make

    In your Make scenario, add any Reply Agent module and click Create a connection. A connection is your Reply Agent account linked to Make once, then reused by every Reply Agent module you add later.

  3. 03

    Paste the key and save

    Give the link a clear label in the Connection name field if you want (it is optional, but it helps when you manage several workspaces). Paste your API key, confirm, and Make can now read your contacts.

First scenario

Your first scenario with Reply Agent

GoalWhen a new contact appears in Reply Agent, Make tags it and sends it a Smart Flow.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place your first module on the canvas.

  2. 02

    Pick the Watch New Contacts trigger

    Search for Reply Agent, choose Watch New Contacts and select the connection you created. This module starts the scenario each time Make finds contacts it has not seen yet.

  3. 03

    Add Apply a Tag

    Click the + on the right of the trigger and add Apply a Tag. Map the contact from the trigger, then choose the tag your team uses for newcomers.

  4. 04

    Chain Send a Smart Flow

    Add Send a Smart Flow after the tag, map the same contact again and pick the flow that should welcome new people. Each contact is one bundle, one item passed from module to module.

  5. 05

    Test with Run once

    Create a test contact in Reply Agent, then click Run once. Open the bubbles above each module to read the bundles it received and check that the tag and the flow landed.

  6. 06

    Schedule and switch it on

    Click the clock on the first module to set Scheduling (every 15 minutes by default), then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

What starts a Reply Agent scenario

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

Reply Agent1Watch New Contacts

Watch New Contacts

triggerIn the docs only

Every contact added to Reply Agent since the last check reaches your scenario as its own bundle, ready to be tagged, enriched or sent a flow. It is the only Reply Agent trigger in Make, so most scenarios that start from Reply Agent begin here.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default and never more often than that on the Free plan.
When to use it
you want each newcomer greeted, labeled or copied to another tool without anyone watching the contact list.
Watch out
as its name says, it watches new contacts; do not count on it to react when you edit an existing one.
Modules

What Reply Agent can do in Make

Reply Agent gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Reply Agent1

Add a Contact

ActionIn the docs only

People who sign up in another app appear in Reply Agent without anyone copying them over. Place this action after a form, a shop order or a booking tool, and map the details that app provides.

When to use it
your leads start life outside Reply Agent and you want them reachable there too.
Watch out
if another scenario starts from Watch New Contacts, every contact you add here will start that one too. Plan for it.
Reply Agent2

Apply a Tag

ActionIn the docs only

A contact gets a label the moment something happens elsewhere, so your lists and segments stay accurate without manual sorting. Map the contact, pick the tag, and the action does the rest.

When to use it
a payment clears, a demo is booked or a ticket closes, and that event should change how you treat the person.
Watch out
the Make doc gives no detail on tags that do not exist yet, so create them in Reply Agent first.
Reply Agent3

Get a Contact

ActionIn the docs only

You pull up one contact whose identifier you already have, so later modules can use details the trigger did not carry. One contact in, one bundle out.

When to use it
another app hands you a Reply Agent contact reference and you need the rest of that person's information before deciding what to do.
Watch out
without an identifier, use Search Contacts by a Custom Field instead.
Reply Agent4

Make an API Call

ActionIn the docs only

Anything the Reply Agent API offers becomes reachable from your scenario, even when no dedicated module covers it. No second key to manage: the call rides on the connection you already set up.

When to use it
you checked the eight other modules and none of them does the job you need.
Watch out
you write the request yourself, so keep the Reply Agent API reference open while you build it.
Reply Agent5

Remove a Tag

ActionIn the docs only

Stale labels disappear on their own, so a contact who moved on is no longer counted in the wrong segment. It is the natural counterpart of Apply a Tag and usually sits right next to it.

When to use it
a trial ends, a subscription is cancelled or a lead turns into a customer, and the old tag now sends the wrong message.
Watch out
map the right contact carefully, since the doc says nothing about undoing the change.
Reply Agent6

Search Contacts by a Custom Field

SearchIn the docs only

This search finds the people whose custom field holds a given value, for example an order number or an account ID stored in Reply Agent. It can return zero, one or several bundles.

When to use it
the event comes from another tool that knows your own reference, not the Reply Agent contact ID.
Watch out
when several contacts match, every following module runs once per contact, and each run costs operations.
Reply Agent7

Send a Smart Flow

ActionIn the docs only

A conversation you designed in Reply Agent starts for a contact because of an event in another app, not because someone remembered to launch it. You prepare the Smart Flow in Reply Agent, and Make picks the moment.

When to use it
a new contact should be welcomed, or a customer who just paid should receive the next steps.
Watch out
the doc does not describe the flow settings, so test it on your own contact with Run once first.
Reply Agent8

Set a Custom Field

ActionIn the docs only

Your Reply Agent records hold the information your other tools already know, such as a plan name or a customer reference. Map the contact, choose the field, pass the value from an earlier module.

When to use it
you want replies and flows in Reply Agent to rely on data that lives in your CRM or your shop.
Watch out
the field must already exist in Reply Agent; this module fills it, the doc does not say it creates one.
Need help

Need help automating Reply Agent with Make?

A person reads every message.

FAQ

Reply Agent and Make: common questions

01Is the Reply Agent Make integration free?
Yes, on the Make side. Reply Agent is a standard app, available from the Free plan onward. That plan has real limits though: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. You still need your own active Reply Agent account, which is billed by Reply Agent, not by Make.
02What do you need to connect Reply Agent to Make?
Two things: an active Reply Agent account and an API key from it. In Reply Agent, go to Settings, then Connect in the sidebar, then API, and click Generate Key if no key exists yet. Copy it. In Make, add any Reply Agent module, click Create a connection, give it a name if you like and paste the key. That single connection then serves all 9 Reply Agent modules, so you only do this once per account.
03Does the Reply Agent Watch New Contacts trigger fire instantly?
No. Watch New Contacts is a scheduled trigger: Make checks Reply Agent on the scenario's schedule, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval allowed. Paid plans can go down to 1 minute. There is no instant Reply Agent trigger in Make, so if you need a faster start, launch the scenario from another app that calls Make and then use the Reply Agent actions, such as Get a Contact or Apply a Tag, to act on the contact.
04What if a Reply Agent module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Reply Agent API from your scenario and reuses the connection you already created, so nothing new to set up on the account side. Start by checking the 8 other modules: contacts, tags, custom fields, a search and Smart Flows are covered. Keep in mind that the Make documentation for Reply Agent is brief and flagged as generated from the vendor docs, so confirm any important behavior with Reply Agent directly.
05Should you use Make or n8n for Reply Agent?
It depends on what each tool offers for Reply Agent when you check. On Make, you get the 9 modules described here, including a scheduled trigger for new contacts and Make an API Call for the rest of the API, all built in a visual editor. The same app often has an n8n node too, but confirm it exists and compare its operations before choosing. Pick the tool whose Reply Agent coverage matches the scenarios you plan to build, and the one your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations