Resources · Make integration

SatisMeter Make integrationAutomate SatisMeter with Make.

Can Make act on every new SatisMeter response for you? Yes. The SatisMeter Make integration gives you 12 modules: 1 scheduled trigger, 9 actions and 2 searches. This guide helps you link your account and build a first scenario step by step.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SatisMeter Make integration do for you?

The SatisMeter Make integration lets Make read and write your SatisMeter data without code. You build a scenario, which is the automation itself: a chain of modules, each one a single brick such as a trigger, an action or a search. Make then runs it on a schedule and passes each response or user along the chain.

Keep your user base in sync. When someone signs up in your product or CRM, Create / Update a User adds them to SatisMeter or refreshes their record, and Track an Event logs what they just did. Your surveys then reach people with up-to-date information.

Route fresh feedback to the right person. Watch New Response picks up each new response, and Get a User pulls the matching profile so the next module can post it where your support or product team works.

Respect opt-outs everywhere. Get a List of Unsubscribed Emails reads who stopped hearing from SatisMeter, and Update a List of Unsubscribed Emails pushes opt-outs collected elsewhere back into it.

The documentation lists no specific limits for these modules, and it flags itself as AI-generated content to verify against SatisMeter's own docs. When a need goes beyond the 12 modules, Make an API Call reaches other endpoints with the same connection. Before choosing a tool, the n8n vs Make comparison lays out the criteria, Make pricing explains how operations are counted, and Make training helps if scenarios are new to you.

Connect

How do you connect SatisMeter to Make?

  1. 01

    Copy your Write key

    In SatisMeter, open Settings, then Integrations, then API keys. Copy the key labeled Write key. You need an active SatisMeter account to see these keys.

  2. 02

    Start a connection in Make

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several workspaces. Paste the Write key you copied, confirm, and Make can now read and write your SatisMeter data.

First scenario

Your first scenario: add new signups to SatisMeter

GoalWhen a new customer appears in another app, Make creates or updates the user in SatisMeter and records the event.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. This first brick will be the app where your new customers show up, such as your CRM or store.

  2. 02

    Add the SatisMeter user module

    Click the + on the right, search SatisMeter and pick Create / Update a User. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the customer data

    Fill the module fields with data from the first module: Make lets you click the values it received and drop them in. Each customer that passes through is a bundle, one item flowing from module to module.

  4. 04

    Log the event

    Add Track an Event after the user module so SatisMeter knows what this person just did. Map the same user so the event lands on the right profile.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check that the user and the event look right in SatisMeter.

  6. 06

    Schedule and switch it on

    Open Scheduling on the first module. A new scenario runs every 15 minutes by default. Keep it or pick another interval allowed by your plan, then switch the scenario on.

Triggers

What can start a SatisMeter scenario?

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

SatisMeter1Watch New Response

Watch New Response

Scheduled trigger

In MakeTriggers when a new response is created.

Watch New Response hands your scenario every response people submit in SatisMeter, one bundle per response, so feedback reaches the tools where your team actually works instead of waiting in a dashboard.

How it fires
it is a scheduled trigger. Make checks SatisMeter on the scenario's schedule, every 15 minutes by default, and collects the responses created since the last check.
When to use it
when each new response should reach a support queue, a shared channel or a follow-up list.
Watch out
this is not real time; on the Free plan the shortest gap between two checks is 15 minutes.
Modules

What else can Make do in SatisMeter?

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

SatisMeter1

Create a Response

Action

In MakeCreates a response.

Create a Response adds a response to SatisMeter from inside a scenario, which keeps feedback gathered elsewhere, on a form or in a support tool, in the same place as your surveys.

When to use it
when answers come in through another channel and you still want SatisMeter to hold them.
SatisMeter2

Create / Update a User

Action

In MakeCreates or updates a user.

Create / Update a User gives you one module for both cases: a new person gets a SatisMeter profile, and someone already there gets refreshed details, so you never check first whether they exist.

When to use it
right after a signup or a profile change in your product or CRM.
Watch out
run it once on someone already in SatisMeter and check that their record was updated, not added twice.
SatisMeter3

Delete a User

Action

In MakeDeletes a user.

Delete a User removes a person from SatisMeter, which helps you honor a closed account or a deletion request without opening the app by hand.

When to use it
when an account is closed in your main system and the profile must disappear from SatisMeter too.
Watch out
the scenario deletes without you opening SatisMeter to confirm, so test it on a dummy user with Run once first.
SatisMeter4

Get a List of Unsubscribed Emails

Action

In MakeGets a list of unsubscribed emails.

Get a List of Unsubscribed Emails tells you which addresses opted out of SatisMeter, so the rest of your stack can stop contacting them as well.

When to use it
before sending a campaign from another tool, to copy SatisMeter opt-outs into your mailing platform or CRM.
Watch out
it only reads the list; to change it from Make, use Update a List of Unsubscribed Emails instead.
SatisMeter5

Get a Response Statistics

Action

In MakeGets a response statistics.

Get a Response Statistics brings back the summary figures SatisMeter computes on your responses, so a report or a spreadsheet can show them without anyone exporting data by hand.

When to use it
when you want those figures copied into a team dashboard or a status message that other people read.
SatisMeter6

Get a User

Action

In MakeGets a user.

Get a User fetches one SatisMeter profile so the next modules know who they are dealing with, which is handy to add context to a response before sharing it.

When to use it
after Watch New Response, when the alert you send should include the person behind the answer.
Watch out
it reads a single user; to scan many, List Users fits better.
SatisMeter7

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call lets you reach any endpoint of the SatisMeter API with the connection you already set up, so a missing module does not block your scenario.

When to use it
when none of the other 11 modules covers what you need and the SatisMeter API documentation shows the request to send.
Watch out
you write the request yourself, so check the method and path in the vendor documentation first.
SatisMeter8

Track an Event

Action

In MakeTracks an user event.

Track an Event records something a user did in SatisMeter, which gives your surveys a clearer picture of each person's activity in your product.

When to use it
when an action in another app, such as an upgrade or a completed order, should be logged against the user in SatisMeter.
Watch out
create the user first with Create / Update a User if they may not exist yet.
SatisMeter9

Update a List of Unsubscribed Emails

Action

In MakeUpdates a list of unsubscribed emails.

Update a List of Unsubscribed Emails sends opt-outs back to SatisMeter, so someone who left your newsletter elsewhere stops getting surveys too.

When to use it
when your email platform or preference center records an unsubscribe and SatisMeter must follow.
Watch out
this changes who SatisMeter may contact; try it on a test address with Run once before switching the scenario on.
SatisMeter10

List Responses

Search

In MakeGets all responses.

List Responses pulls the responses stored in SatisMeter in one pass, which suits a full export or a catch-up after your scenario was paused.

When to use it
when you need past responses too, not only the new ones Watch New Response picks up.
Watch out
it is a search, so it can return zero, one or many bundles, and every module after it runs once per bundle.
SatisMeter11

List Users

Search

In MakeReturns the list of all users in a project.

List Users returns every user of a SatisMeter project, giving you the full audience to compare with your CRM or to clean up in bulk.

When to use it
when you audit which profiles SatisMeter holds against another system of record.
Watch out
each user comes out as its own bundle, and each module that follows spends one operation per user.
Need help

Need help automating SatisMeter with Make?

A person reads every message.

FAQ

SatisMeter and Make: common questions

01Is the SatisMeter Make integration free?
Yes, on the Make side. SatisMeter is a standard app, available from the Free plan like the 3,000+ standard apps on every plan. The Free plan allows 2 active scenarios, a shortest gap of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Each module run on a bundle counts as one operation on your plan. Paid plans lower the interval to 1 minute and remove the active scenario cap. Your SatisMeter subscription is a separate matter, covered on the SatisMeter pricing page.
02What do you need to connect SatisMeter to Make?
You need an active SatisMeter account and its API key. In SatisMeter, go to Settings, then Integrations, then API keys, and copy the key labeled Write key. In Make, add a SatisMeter module, click Create a connection, optionally give it a name, and paste the key. The connection is then shared by every SatisMeter module in your scenarios, so this setup happens only once per account. If you later add another SatisMeter module, pick the existing connection from the list instead of pasting the key again.
03Does the SatisMeter Make trigger work in real time?
No. Watch New Response is a scheduled trigger: Make checks SatisMeter on the scenario's schedule and picks up the responses created since the previous check. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans let you go down to 1 minute. If a short delay matters for your follow-up process, pick a paid plan and tighten the schedule on the first module.
04What if a SatisMeter module is missing in Make?
Use Make an API Call. It sends any request the SatisMeter API accepts, with the same connection as the other modules, so you are not stuck with the 11 listed actions and searches. Check the SatisMeter API documentation for the request to send. The Make documentation for this app lists no specific limits, and it notes that its content is AI-generated, so verify important details with SatisMeter directly. If the API call fails, the Make troubleshooting guide is a good first stop.
05Should you use Make or n8n for SatisMeter?
It depends on your criteria. On Make, SatisMeter comes with 12 ready modules, including a scheduled trigger for new responses and Make an API Call for the rest, and it works from the Free plan. The same app often has an n8n node too, so check whether the node covers the actions you need, then compare how each tool counts usage and how your team prefers to build. Neither choice changes what SatisMeter itself can do. Whichever you pick, start with one small scenario and test it with Run once.