Resources · Make integration

InMoment Make integrationAutomate InMoment with Make.

What happens to an NPS answer after the customer clicks submit? With the InMoment Make integration, it can travel on its own: 12 modules, one instant trigger, nine actions and two searches. This guide is for support and CX teams, and it walks you from connection to a first live scenario.

Try the InMoment integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the InMoment Make integration do for your team?

The InMoment Make integration links your InMoment account to Make, a no-code tool where you build a scenario: the automation you assemble from bricks called modules. InMoment then passes each new survey response to your other apps, and your other apps can create, update or clean up end users and responses in InMoment.

Detractors reach a human while the answer is still fresh. Watch New Response wakes the scenario as soon as a survey answer lands, Get an End User pulls up who wrote it, and a module from your help desk or chat app opens the follow-up. Nobody has to refresh a dashboard to spot an unhappy customer.

Your survey audience stays in step with your CRM. When a deal closes or a contact changes in another app, Create an End User or Update an End User keeps InMoment aligned, so the next survey goes to the right people.

Privacy requests get handled in one pass. List Responses finds everything a person submitted, Delete a Response removes each answer, and Delete an End User schedules the account for removal.

Make publishes only limited documentation for this app: it says there is not enough public information about InMoment to write a complete guide. Test every module with your own account before relying on it. If you also look at n8n, the n8n vs Make comparison lays out the criteria, and the Make training covers the editor from zero. For costs on the Make side, see Make pricing.

Connect

How do you connect InMoment to Make?

  1. 01

    Open a connection from any InMoment module

    In a scenario, add any InMoment module and click Create a connection. A connection is your InMoment account linked to Make once; every InMoment module in every scenario reuses it afterwards.

  2. 02

    Give it a name you will recognize

    Naming the connection is optional, but worth doing. If your company runs more than one InMoment account, a clear label such as the team or region saves you from picking the wrong one later.

  3. 03

    Authorize Make, then save

    Either approve Make on the InMoment page that opens, or paste the key InMoment gives you, depending on what the window asks for. Click Save, and Make can now read and write in your account.

First scenario

Build your first scenario with InMoment

GoalWhen a customer submits an NPS response in InMoment, Make fetches that person's end user record so your team knows who answered.

  1. 01

    Start a blank scenario

    Go to the Scenarios page, create a new scenario and click the big + in the middle of the editor to place the first module.

  2. 02

    Add Watch New Response

    Search for InMoment, choose Watch New Response and link your account with Create a connection. This trigger carries the lightning badge: InMoment will call Make on its own.

  3. 03

    Chain Get an End User

    Click the + to the right of the trigger and pick Get an End User. In its ID field, map the end user ID found in the bundle the trigger hands over, so the lookup targets the person who answered.

  4. 04

    Test with Run once

    Click Run once, then submit a test answer to your survey. Open the bubbles above each module to read the bundles, meaning the items that moved from one brick to the next.

  5. 05

    Switch the scenario on

    Once the test looks right, turn the scenario on. From then on, every new response travels through it without anyone touching the editor.

Triggers

What starts an InMoment scenario?

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

InMoment1Watch New Response

Watch New Response

Instant trigger

In Make“Triggers when a new NPS survey response is submitted.”

Watch New Response gets your scenario moving the moment a customer submits an NPS survey answer, so the feedback reaches the right person while it still matters. Each response becomes one bundle for the modules that follow.

How it fires
instant, meaning InMoment calls Make through a webhook as soon as the response is submitted, instead of Make checking on a schedule.
When to use it
any flow that should react to a fresh answer, such as routing a low score to support or logging praise for the marketing team.
Watch out
Make documents this app only partially, so test the trigger with a real survey answer before you depend on it.
Modules

What can Make do in InMoment?

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

InMoment1

Create an End User

Action

In Make“Creates a new end user.”

Create an End User adds a new person to InMoment from another app, so they become someone you can survey without typing them in by hand.

When to use it
a new customer signs up or a deal closes in your CRM, and you want that contact ready for the next survey wave.
Watch out
if the person may already exist, run List End Users first to avoid creating a duplicate.
InMoment2

Create a Response

Action

In Make“Creates a response for the end user.”

Create a Response records an answer in InMoment for an existing end user, which lets feedback collected elsewhere land in the same place as your survey results.

When to use it
a customer gives a score through a form, a chat or a call, and you want it counted alongside the rest of your NPS data.
Watch out
the response belongs to an end user, so create or find that person earlier in the scenario.
InMoment3

Delete an End User

Action

In Make“Deletes the end user. Deletion would be performed the following day at 7 AM UTC.”

Delete an End User removes a person from InMoment, which is how you honor an erasure request without logging in yourself.

When to use it
a customer asks to be forgotten, or leaves and must no longer receive surveys.
Watch out
the deletion is not immediate. InMoment carries it out the following day at 7 AM UTC, so a lookup right after the scenario can still find the person.
InMoment4

Delete a Response

Action

In Make“Deletes an end user response.”

Delete a Response wipes one survey answer from InMoment, for the cases where a single entry has to go but the person stays.

When to use it
a test submission slipped into production data, or a customer asks to withdraw one specific answer.
Watch out
Make has no module to restore a deleted response, so point the module at an exact response ID and run it once on a test record first.
InMoment5

Get an End User

Action

In Make“Gets a specific end user by ID.”

Get an End User fetches one person's record from InMoment by ID, giving the rest of the scenario the details it needs about who answered.

When to use it
right after Watch New Response, to learn who submitted the answer before alerting an account manager.
Watch out
it needs the ID, not a name; when you only have partial details, List End Users is the better start.
InMoment6

Get a Response

Action

In Make“Gets a specific response.”

Get a Response reads one specific survey answer back from InMoment, so a later step can work with its full content rather than a summary.

When to use it
a ticket or a CRM note references a response, and you want to pull that exact answer into a message for your team.
Watch out
it returns a single answer; for everything a person has submitted, reach for List Responses.
InMoment7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the InMoment API from your scenario, reusing the same connection as the other modules, so you are not stuck when a ready-made module is missing.

When to use it
the eleven named modules do not cover what you need and the InMoment API does.
Watch out
you write the request yourself, so keep the InMoment API reference open and test with Run once before activating.
InMoment8

Update an End User

Action

In Make“Updates the end user with specified params.”

Update an End User changes an existing person's record in InMoment, keeping your survey audience accurate as customers move through their lifecycle.

When to use it
a contact's details change in your CRM or billing tool, and you want InMoment to reflect it before the next survey goes out.
Watch out
the module edits a person you already know by ID, so place Get an End User or List End Users upstream.
InMoment9

Update a Response

Action

In Make“Updates an existing response.”

Update a Response edits an answer that already sits in InMoment, which helps when a record needs fixing after the fact instead of being deleted.

When to use it
your team has followed up with a customer and wants the response record to carry that correction.
Watch out
you overwrite what was stored, so read the current version with Get a Response first if you need to keep a trace of it.
InMoment10

List End Users

Search

In Make“Gets all end users.”

List End Users returns the people stored in InMoment, and each one leaves the module as its own bundle for the steps that follow.

When to use it
you want to sync your whole survey audience into a spreadsheet or check whether someone exists before creating them.
Watch out
as a search, it can return zero, one or many people, and every later module runs once per person, which adds operations.
InMoment11

List Responses

Search

In Make“Gets all responses for a user.”

List Responses gathers every answer a given end user has submitted, giving you their full feedback history in one pass.

When to use it
an account manager prepares a renewal meeting, or a privacy request requires finding all answers before deletion.
Watch out
it works per user, not across the whole account, and each answer it returns counts as a separate bundle downstream.
Need help

Need help automating InMoment with Make?

A person reads every message.

FAQ

InMoment and Make: frequent questions

01Is the InMoment Make integration free?
Yes, InMoment is a standard app in Make, so its modules are available on the Free plan. The Free plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lift the interval to 1 minute, remove the cap on active scenarios and count usage in credits, which are operations, per month. Your InMoment subscription is a separate matter that Make does not cover.
02What do you need to connect InMoment to Make?
An InMoment account and access to authorize Make. Make's documentation for InMoment lists no prerequisites and no official connection steps, so the generic path applies: add an InMoment module, click Create a connection, optionally name it, approve Make on the InMoment page or paste the key InMoment provides, then save. The documentation is flagged as limited because too little public information exists about the app, so ask your InMoment admin if the authorization is refused.
03Does the InMoment trigger in Make react in real time?
Yes. Watch New Response is an instant trigger: InMoment calls Make through a webhook as soon as a customer submits an NPS survey answer, and the scenario starts right away. It does not wait for a schedule, unlike scheduled triggers, which Make checks every 15 minutes by default. In the editor you will see a lightning badge on the module rather than a clock. It remains the only trigger of the app, so other events have to be caught from another app's side.
04What if an InMoment module is missing in Make?
Use Make an API Call. It calls any endpoint of the InMoment API with the same connection as the other modules, which covers most gaps in the 12 ready-made modules. You write the request yourself, so the InMoment API reference becomes your guide. Keep in mind that Make's own documentation for this app is limited, so there are no published limits or troubleshooting notes to lean on; test each request with Run once before switching the scenario on.
05Should you pick Make or n8n for InMoment?
It depends on where the rest of your automations live. Make offers InMoment as a standard app with 12 modules, including an instant trigger on new responses, and it works from the Free plan. Before choosing n8n instead, check whether it offers a node for InMoment and what that node covers. The honest criteria are the modules you need, the tool your team already knows and where your other scenarios run, rather than any general ranking of the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations