Resources · Make integration

Retently Make integrationAutomate Retently with Make.

Can survey feedback from Retently reach the rest of your customer tools on its own? Yes. The Retently Make integration gives you 9 modules: 1 scheduled trigger, 7 actions and 1 search. This page walks support and customer success teams from the connection to a first working scenario.

Try the Retently integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Retently Make integration automate?

The Retently Make integration links your Retently account to Make, a no-code tool where you build a scenario: the automation itself, made of modules. A module is one brick that watches, creates or searches something in an app. With it, customers and survey responses move between Retently and your other tools without copy and paste.

Every new customer gets a survey. When a deal closes in your CRM, Create Customers and Send Survey adds the person to Retently, or updates the record if it already exists, and sends a transactional survey in the same step.

Responses get sorted. Watch Survey Responses picks up new answers on the scenario's schedule, and Tag a Survey Response labels each one so the team knows which ones need a follow-up call.

Customer records stay clean. Update a Customer, Unsubscribe Customers and Delete a Customer keep Retently in line with your main system when someone's details change, when they opt out, or when they leave.

What Make does not do here: there is no instant trigger, so a response reaches Make at the next scheduled check, not the moment it is submitted. Anything the listed modules skip goes through Make an API Call. Make's own Retently documentation also says it was generated by AI, so confirm important details with Retently. The same app often has an n8n node; the n8n vs Make comparison lays out the criteria. New to the editor? Start with the Make training, and keep Make troubleshooting close for failed runs.

Connect

How do you connect Retently to Make?

  1. 01

    Add a Retently module

    In your scenario, click the +, search for Retently and pick any of its modules. Then click Create a connection. A connection is your Retently account linked to Make once, and every Retently module reuses it afterwards.

  2. 02

    Name the connection

    The Connection name field is optional. A clear name still saves confusion if you handle more than one Retently account, for example a test account next to the live one.

  3. 03

    Paste your API key

    You need an active Retently account and its API key. In Retently, open the account dashboard, click Settings, then the API section or the API keys tab, and copy the key shown. Paste it into Make to finish.

First scenario

Your first scenario: tag every new Retently response

GoalWhen a new survey response lands in Retently, Make tags it so your team can find it later.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor. This first module is the one that starts everything else.

  2. 02

    Add the trigger

    Search for Retently, choose Watch Survey Responses and select the connection you made earlier. Once connected, Make lists what it can read from your account, so you pick instead of typing.

  3. 03

    Add the tag action

    Click the + on the right of the trigger, pick Tag a Survey Response and map the response coming from the previous module. Then type the tag your team will filter on in Retently.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, a bundle being one item passed from a module to the next. Check the tag in Retently.

  5. 05

    Schedule and switch it on

    Open the clock on the first module, Scheduling. Keep the default of every 15 minutes or pick another interval your plan allows, then switch the scenario on.

Triggers

What starts a Retently scenario

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

Retently1Watch Survey Responses

Watch Survey Responses

Scheduled trigger

In Make“Watches for survey responses”

Each fresh answer to one of your Retently surveys lands in the scenario through Watch Survey Responses, so the modules after it can act on what a customer just told you.

How it fires
it is a scheduled trigger. Make checks the app on the scenario's schedule, every 15 minutes by default and down to every minute on paid plans.
When to use it
whenever a response should lead somewhere, such as a tag, a CRM update or a note to the account owner.
Watch out
a response does not appear the moment the customer submits it, it waits for the next scheduled check.
Modules

What each Retently module does

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

Retently1

Create a Customer

Action

In Make“Creates a customer.”

Create a Customer adds one new person to Retently from data produced by an earlier module, without sending them a survey yet.

When to use it
a signup on your website or a new account in your billing tool should become a Retently customer.
Watch out
this module sends nothing; if the survey should go out as well, Create Customers and Send Survey is the right pick.
Retently2

Create Customers and Send Survey

Action

In Make“Creates new customers or updates the existing ones and send a transactional survey.”

Two jobs in one module: it creates customers, or updates those already in Retently, and right after that sends them a transactional survey.

When to use it
an order is delivered or a support ticket is closed, and that is exactly the moment you want feedback.
Watch out
every run sends a survey, so place it behind the event that truly deserves one.
Retently3

Delete a Customer

Action

In Make“Deletes a customer.”

Delete a Customer removes a person from Retently when your main system says they should no longer be there.

When to use it
a customer asks for their data to be erased, or a test contact slipped into your live account.
Watch out
a deletion is not something to try on real records; do your Run once on a test customer before switching the scenario on.
Retently4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Retently API with the connection you already set up, for everything the eight other modules leave out.

When to use it
you need a Retently feature that has no dedicated module in Make.
Watch out
you talk to the API directly here, so keep the Retently API documentation open to know what to send.
Retently5

Tag a Survey Response

Action

In Make“Adds a tag to a survey response.”

A label on each answer turns a raw stream of feedback into piles your team can filter, and that is what Tag a Survey Response does.

When to use it
right after Watch Survey Responses, to mark the answers that call for a follow-up.
Watch out
settle on tag names once and reuse them exactly, or the same idea ends up split across several tags.
Retently6

Unsubscribe Customers

Action

In Make“Unsubscribes customers.”

Unsubscribe Customers marks people as unsubscribed in Retently, so your surveys respect a choice they made in another tool.

When to use it
someone opts out in your email tool or your CRM, and Retently should follow without anyone updating it by hand.
Watch out
unsubscribing and deleting are two separate modules; pick Delete a Customer only when the record itself must go.
Retently7

Update a Customer

Action

In Make“Updates a customer.”

When a customer's details change, Update a Customer corrects their record in Retently, so survey results stay tied to accurate information.

When to use it
a contact's details are edited in your CRM and Retently needs to reflect the change.
Watch out
the module works on an existing customer; if in doubt, run List Customers first to confirm the person is there.
Retently8

List Customers

Search

In Make“Returns a list of customers with specified fields.”

List Customers returns the Retently customers that match your request, with the fields you choose to bring back, ready for the next module.

When to use it
before an update or a deletion, to see who is already in Retently.
Watch out
it is a search, so it can return zero, one or several bundles; plan for each case before mapping the result.
Need help

Need help automating Retently with Make?

A person reads every message.

FAQ

Questions about the Retently Make integration

01Is the Retently Make integration free?
Yes, on the Make side. Retently is a standard app, so it works 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 plans (Core, Pro, Teams and Enterprise) bring the interval down to one minute and lift the cap on active scenarios. Usage is counted in operations, one operation being one module run on one item. You still need an active Retently account.
02What do you need to connect Retently to Make?
An active Retently account and its API key. You find the key in Retently by opening the account dashboard, then Settings, then the API section or the API keys tab. In Make, add any Retently module, click Create a connection, give it a name if you like, and paste the key. That connection is then reused by every Retently module in your scenarios, so the setup happens only once per account.
03Does the Retently trigger run as soon as a response arrives?
No. Watch Survey Responses is a scheduled trigger: Make checks Retently on the scenario's schedule, and Retently does not alert Make. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to one minute. In the editor, the clock badge on the module reminds you of this. If your team needs a quicker reaction, shorten the schedule on a paid plan.
04What if a Retently module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Retently API with the connection you already have, so there is nothing new to set up. First check that the 8 other modules do not already cover the job: creating, updating, unsubscribing, deleting and listing customers, tagging responses and sending a transactional survey. Keep in mind that Make's Retently documentation says it was generated by AI, so confirm important details with Retently.
05Make or n8n for Retently?
It depends mostly on where your other automations already live. In Make, Retently comes with 9 modules, a scheduled trigger for survey responses and Make an API Call for everything else. The same app often has an n8n node too, so compare its modules with your use case before choosing. The most practical criterion is to build in the tool your team already uses, so every scenario sits in one place with a single tool to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations