Resources · Make integration

Refiner Make integrationAutomate Refiner with Make.

What happens to a survey answer once Refiner has collected it? The Refiner Make integration gives you 6 modules, including 2 instant triggers, to push answers and user data into the rest of your stack. This page walks you through the connection, a first scenario and every module.

Try the Refiner integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the Refiner Make integration?

The Refiner Make integration links your Refiner account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. Refiner can start a scenario the moment a survey is completed or a user joins a segment, and Make can send user profiles and events back to Refiner.

Route every survey answer where the team reads it. Watch Completed Survey fires as soon as someone finishes a survey. Add the module of your helpdesk, your spreadsheet or your chat tool behind it, and each answer lands there without anyone copying it by hand.

Keep Refiner profiles in step with your CRM. When a customer record changes in another app, Identify a User creates or updates that person in Refiner, so your targeting uses fresh attributes. Track an Event adds the actions they performed, which your survey rules can then rely on.

React when a user lands in a segment. Watch User Entered Segment tells Make who just matched one of your segments, which is a clean moment to alert an account manager or tag the contact elsewhere.

Know the edges before you start. Only these 6 modules are listed, and anything else goes through Make an API Call. The official documentation page itself warns that its content is AI-generated from Refiner's docs and may contain mistakes, so check important details with Refiner. Many apps also have an n8n node, so check whether Refiner does; the n8n vs Make comparison lays out both tools side by side. New to the editor? The Make training starts from zero, and the Make pricing page explains how operations are counted.

Connect

How do you connect Refiner to Make?

  1. 01

    Copy your API key in Refiner

    You need an active Refiner account and its API key. In Refiner, open the dashboard, go to Integrations, then Rest API, and copy the key shown on screen. Keep it at hand for the next step.

  2. 02

    Add a Refiner module in Make

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

  3. 03

    Paste the key and save

    Paste the API key you copied from Refiner, or follow the instructions Make shows on screen, then save. Make now lists what it can read from your account, so you can pick values from menus instead of typing them.

First scenario

Your first scenario with Refiner and Make

GoalWhen a customer record changes in another app, Make creates or updates that person in Refiner and logs the matching event.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app that holds your customer records, such as your CRM, and its module that watches new or updated contacts.

  2. 02

    Add Identify a User

    Click the + on the right of that first module, search for Refiner and choose Identify a User. Connect your account, then map the customer data coming from the previous module into the fields Make displays.

  3. 03

    Log the event

    Add Track an Event after it, still with the same Refiner connection. Map the same person so Refiner attaches the event to the profile that the step before just created or refreshed.

  4. 04

    Test with Run once

    Click Run once: Make executes the scenario a single time. Open each module to read the bundles it received, a bundle being one item passed along, here one customer. Then check the profile in Refiner.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From there, each changed record keeps its Refiner profile up to date without any copying.

Triggers

Which Refiner triggers start a scenario?

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

Refiner1Watch Completed Survey

Watch Completed Survey

Instant trigger

In Make“Triggers when a survey is completed.”

This trigger hands you each survey response the moment a respondent submits it, so the answer can travel straight to the tool where someone will act on it. Every completed survey becomes one bundle for the modules that follow.

How it fires
instant, meaning Refiner calls Make through a webhook as soon as the survey is completed, with no waiting for a schedule.
When to use it
a low satisfaction score has to reach the support queue or the account owner before the customer moves on.
Watch out
click Create a webhook before Create a connection: the documentation gives that order for instant modules.
Refiner2Watch User Entered Segment

Watch User Entered Segment

Instant trigger

In Make“Triggers when a user has entered the segment.”

Here the starting point is a person rather than an answer: Make receives the user who has just entered one of your Refiner segments. That lets a segment you already defined in Refiner drive work in other tools.

How it fires
instant, because Refiner notifies Make by webhook the moment the user joins the segment.
When to use it
a trial account matches your "ready to upgrade" segment and the sales rep should hear about it while the signal is fresh.
Watch out
the trigger follows the segment rules set in Refiner, so a badly scoped segment floods the scenario and burns operations, each operation being one module run that Make counts on your plan.
Modules

What can Make do in Refiner?

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

Refiner1

Identify a User

Action

In Make“Creates a new user in Refiner or updates an already existing user.”

You get a Refiner profile that matches reality: the module creates the user when Refiner does not know them yet and updates the existing record otherwise. One module covers both cases, with no search beforehand.

When to use it
a customer changes plan or company in your CRM and Refiner should target surveys with the new details.
Watch out
since the module also updates existing users, map only data you trust.
Refiner2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module opens the rest of the Refiner API to your scenario, reusing the connection you already created. It is the way to reach anything that the other five modules do not cover.

When to use it
you need a Refiner feature that has no dedicated module in the list.
Watch out
you write the request yourself, so keep Refiner's API documentation open and test it with Run once before going live.
Refiner3

Track an Event

Action

In Make“Tracks event performed by users.”

Tell Refiner what a user just did, and the event is added to their history. Refiner then knows about actions that happened outside your product, which your surveys can build on.

When to use it
a purchase, a cancellation or a support ticket is recorded in another tool and should count in Refiner too.
Watch out
the event is tied to a user, so place Identify a User before it when that person may not exist in Refiner yet.
Refiner4

List Contacts

Search

In Make“Lists all contacts.”

Pull the contacts stored in Refiner into your scenario, each one arriving as a separate bundle. That is handy for copying your audience into a spreadsheet or cross-checking it against another database.

When to use it
you want an export of your Refiner contacts without downloading files by hand.
Watch out
this search returns all contacts, and every module placed after it runs once per contact, which multiplies the operations counted on your plan.
Need help

Need help automating Refiner with Make?

A person reads every message.

FAQ

Refiner and Make: frequently asked questions

01Is the Refiner Make integration free?
Yes, Refiner is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 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 such as Core, Pro, Teams and Enterprise bring the interval down to 1 minute and remove the cap on active scenarios. On the Refiner side you still need an active account with API access, which follows Refiner's own subscription.
02What do you need to connect Refiner to Make?
An active Refiner account and its API key. You find the key in the Refiner dashboard under Integrations, then Rest API, where it is displayed on screen. In Make, add a Refiner module, click Create a connection, optionally give the connection a name, and paste the key. For the two instant triggers, create the webhook first and the connection after it. Once saved, that single connection is reused by every Refiner module in all your scenarios.
03Do Refiner triggers react in real time?
Yes. Both Refiner triggers, Watch Completed Survey and Watch User Entered Segment, are instant: Refiner calls Make through a webhook as soon as the survey is completed or the user joins the segment. The scenario therefore does not wait for the 15 minute default schedule that applies to scheduled triggers. Test it by clicking Run once, then completing a survey in Refiner, and the bundle shows up in Make a moment later.
04What if the Refiner module you need is missing in Make?
It depends on what you need. The integration lists 6 modules: 2 triggers, 3 actions and 1 search. For any other Refiner endpoint, use Make an API Call, which sends an authorized request with the connection you already have. You write the request yourself, following Refiner's API documentation. Keep in mind that the Make documentation page for Refiner states it was generated by AI from the vendor's docs, so confirm important behavior directly with Refiner.
05Should you use Make or n8n for Refiner?
It depends on the tool your team already works in. On Make, Refiner comes with 6 modules, 2 of them instant triggers, and Make an API Call covers the rest of the API through the same connection. Many apps also exist as n8n nodes, so first check whether Refiner has one there; if it does, weigh the editor your team prefers and the other apps your scenarios need. Compare the modules each side offers for your use case before building anything large.
Same platform

Other docs you might need on this stack.

Browse all integrations