Resources · Make integration

RepliQ Make integrationAutomate RepliQ with Make.

Can Make launch your RepliQ templates for you? Yes. The RepliQ Make integration gives you 4 modules: 1 trigger and 3 actions. This page walks you through the connection, a first working scenario and what each module is good for.

Try the RepliQ integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the RepliQ Make integration let you automate?

The RepliQ Make integration links your paid RepliQ account to Make so that a scenario, the automation you build in Make, can start your templates, read your remaining credits and notice when a process is done. You set it up once with your account email and API key, then every RepliQ module reuses it.

Outreach that starts on its own. A new prospect lands in your form tool or CRM, and Launch a User Template starts one of your RepliQ templates with that prospect's data mapped in. Nobody has to copy a row by hand.

A clear signal when the work is done. Watch Finished Processes picks up processes that have completed, so the next step (a message to the sales rep, a row in a sheet) happens in the same scenario.

No surprise on your balance. Place Get User Credits Count before a launch and the number of credits left shows up in the data Make passes along, ready to be sent to whoever handles the subscription.

Know the limits before you build. The Make documentation for RepliQ lists these 4 modules and no instant trigger, so finished processes are picked up on the scenario's schedule, not the second they end. The doc itself flags that its RepliQ content was AI-generated and asks you to verify important details with RepliQ. For anything the list does not cover, Make an API Call reaches the rest of the RepliQ API with the same connection.

New to the editor? The Make training starts from zero, and the n8n vs Make comparison helps if you are still picking a tool.

Connect

How do you connect your RepliQ account to Make?

  1. 01

    Copy your email and API key

    In RepliQ, go from your dashboard to the account screen. Two things are displayed there: the email tied to your account and your API key. Copy both somewhere safe, Make will ask for them in a moment.

  2. 02

    Add a RepliQ module

    Open your scenario in Make, add any RepliQ module and click Create a connection. A connection is your RepliQ account linked to Make once and reused by every RepliQ module. The Connection name field is optional, a clear name helps when you have several accounts.

  3. 03

    Paste the credentials

    Enter the email and the API key you copied, or follow the instructions shown on screen, then save. Make now lists what it can read from your account inside each RepliQ module.

First scenario

Build your first RepliQ scenario

GoalWhen a new prospect arrives in another app, Make reads your RepliQ credits and launches one of your templates with that prospect's data.

  1. 01

    Start from the source app

    On the Scenarios page, create a new scenario and click the + to add the first module: the trigger of the app where prospects come in, such as your form tool or CRM.

  2. 02

    Add Get User Credits Count

    Click the + on the right, search RepliQ and pick Get User Credits Count. Click Create a connection and paste your email and API key.

  3. 03

    Add Launch a User Template

    Add Launch a User Template after it. Fill its fields: once the connection exists, Make lists what it can read, and you map the prospect data coming from the first module.

  4. 04

    Test with Run once

    Click Run once and create a test prospect in the source app. Open each module to read the bundle it received, a bundle being one item passed from one module to the next.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run on a bundle costs one operation on your Make plan.

Triggers

What can start a RepliQ scenario?

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

RepliQ1Watch Finished Processes

Watch Finished Processes

triggerIn the docs only

This trigger hands your scenario every RepliQ process that has reached its end, so whatever comes next can run without you checking the RepliQ dashboard. Each finished process travels on as its own bundle.

How it fires
scheduled, Make checks the app on the scenario's schedule. That schedule is the clock on the first module, every 15 minutes by default and never shorter than 15 minutes on the Free plan.
When to use it
when a template launched earlier must lead to a follow-up, like a note for the sales rep or a row added to a sheet.
Watch out
Make lists this module in its doc without a description, and its scheduled type is inferred from the name. Test it with Run once on a real finished process first.
Modules

What can Make do in RepliQ?

RepliQ gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

RepliQ1

Get User Credits Count

ActionIn the docs only

You get the number of credits left on your RepliQ account, delivered as data the next modules can use or send to someone.

When to use it
right before a launch, so the scenario carries your balance and the person who manages the subscription sees it drop.
Watch out
the doc gives no description for this module, so test it with Run once and read the bundle to see exactly what comes back.
RepliQ2

Launch a User Template

ActionIn the docs only

Your RepliQ templates start without a click on your side, as the module's name says, fed with data mapped from earlier modules.

When to use it
when a prospect appears in another app and should get your RepliQ treatment straight away.
Watch out
each run is one operation on your Make plan, and a scenario fed by a large import will launch once per bundle. Try it on a single test record first.
RepliQ3

Make an API Call

ActionIn the docs only

This one opens the rest of the RepliQ API to your scenario, using the connection you already set up, so you are not stuck when the 3 ready-made modules fall short.

When to use it
when you need a RepliQ endpoint that none of the listed modules covers.
Watch out
you describe the request yourself, so keep the RepliQ API documentation open and check the response with Run once.
Need help

Need help automating RepliQ with Make?

A person reads every message.

FAQ

RepliQ and Make: common questions

01Is the RepliQ Make integration free?
On the Make side, yes. RepliQ is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid Make plans lower the interval to 1 minute and remove the cap on active scenarios. On the RepliQ side, the Make documentation asks for a paid RepliQ account, so the integration is not free end to end.
02What do you need to connect RepliQ to Make?
A paid RepliQ account and two pieces of information from it: the email tied to the account and the API key, both shown on the account screen you reach from the dashboard. In Make, add any RepliQ module, click Create a connection, name it if you want, then paste the credentials. The connection is created once and every RepliQ module in your scenarios reuses it, including Make an API Call.
03Does the RepliQ trigger in Make work in real time?
No. Watch Finished Processes is a scheduled trigger: Make checks RepliQ on the scenario's schedule instead of being called the moment a process ends. A new scenario checks every 15 minutes by default. The Free plan cannot go below 15 minutes, while paid plans can go down to 1 minute. If you need a faster reaction, the only lever documented for this app is the schedule itself, since Make lists no instant trigger for RepliQ.
04What if a RepliQ module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the RepliQ API from your scenario with the same connection, which covers what the 3 listed actions and the single trigger leave out. You write the request yourself, so the RepliQ API documentation becomes your reference. Keep in mind that Make notes its RepliQ doc is AI-generated and may contain mistakes, so confirm important details directly with RepliQ before you build on them.
05Should you use Make or n8n for RepliQ?
It depends on which tool your team already runs. On Make, RepliQ comes with 4 modules: 1 scheduled trigger, 2 dedicated actions and Make an API Call for everything else, all behind a single connection. Many apps also exist as an n8n node, but this page does not check whether RepliQ does. Compare the list of available operations on both sides for your use case, and read the n8n vs Make comparison on this site for the general criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations