Resources · Make integration

Delighted Make integrationAutomate Delighted with Make.

What happens to a survey answer once it lands in Delighted? The Delighted Make integration gives you 6 modules: 1 instant trigger, 4 actions and 1 search. This page shows how to link your account, build a first scenario and pick the right module.

Try the Delighted integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Delighted Make integration do?

The Delighted Make integration links your Delighted account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. Delighted brings survey responses into that chain and lets Make send surveys, look people up or remove them, without you opening Delighted.

Survey feedback that reaches the team. Watch Survey Responses starts a scenario as soon as someone answers, and the next module can post that answer wherever your support or product team already works.

Surveys sent from the tools you use. When a deal closes in your CRM or an order ships, Send to People adds or updates that customer in Delighted and schedules the survey email, so nobody has to import a list by hand.

A clean contact base. List People pulls your Delighted contacts into a scenario, Get a Person checks one by email or phone number, and Delete a Person removes someone who asked to leave. For anything these modules skip, Make an API Call reaches the rest of the Delighted API.

The Delighted documentation lists no numeric limits for these modules. If you are still weighing tools, the Make review covers the editor in depth, and n8n vs Make helps when the same app also exists as an n8n node.

Connect

How do you connect Delighted to Make?

  1. 01

    Copy your API key in Delighted

    Log in to Delighted and open Integrations > API. Your API key sits on that page: copy it to your clipboard. It is the only thing Make needs from Delighted, and the documentation lists no other prerequisite.

  2. 02

    Open the connection dialog in Make

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

  3. 03

    Name it and paste the key

    Type a name in Connection name, something you will recognize later, such as the workspace it belongs to. Paste the key into API Key and click Continue. Make can now read and write your Delighted data.

First scenario

Your first scenario with Delighted

GoalWhen a customer answers a Delighted survey, Make looks up that person and passes the details to the next step.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. That empty circle becomes the first module, the one that starts everything.

  2. 02

    Add the trigger

    Search for Delighted, pick Watch Survey Responses and link your account with Create a connection. Because it is an instant trigger, Delighted will call Make as soon as a response comes in.

  3. 03

    Look up the respondent

    Click the + on the right of the trigger and add Get a Person. Map the respondent's email from the trigger, if the response carries one (Run once will show you), so Make fetches that person.

  4. 04

    Test with Run once

    Click Run once, then answer a test survey. Each module shows the bundles it received, a bundle being one item passed along, here one response and then one person.

  5. 05

    Switch the scenario on

    Once the test looks right, add the app where the details should land, then turn the scenario on. From then on, each new response runs it, and each module run counts as one operation on your plan.

Triggers

What starts a Delighted scenario

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

Delighted1Watch Survey Responses

Watch Survey Responses

Instant trigger

In Make“Watches for survey responses.”

This trigger hands your scenario every new survey answer from Delighted, the moment the customer submits it. It is the only Delighted module that can start a scenario, so any flow built on feedback begins here.

How it fires
instant, Delighted calls Make through a webhook as soon as a response arrives, so there is no polling interval to wait for.
When to use it
an unhappy answer that the account manager should see right away, or a written comment that belongs in the product backlog.
Watch out
the scenario must be switched on for Delighted to reach it; while it is off, new answers do not start it.
Modules

What Make can do in Delighted

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

Delighted1

Delete a Person

Action

In Make“Deletes a specified person by email, ID, or phone number.”

Removes one person from your Delighted account, found by email, ID or phone number, so they drop out of your survey audience. You get a contact list that follows what your customers asked for.

When to use it
a customer unsubscribes or closes their account in another tool, and that request should reach Delighted too.
Watch out
a deletion cannot be undone from the scenario, so test it on a dummy contact with Run once first.
Delighted2

Get a Person

Action

In Make“Returns information about a person by email or phone number.”

Fetches the Delighted record of a single person from an email address or a phone number. The next module then works with that profile instead of a bare address.

When to use it
right after a survey response, when you want the full contact before routing the answer, or to check whether someone already exists before sending anything.
Watch out
it looks up one person only; to go through your whole base, List People is the better fit.
Delighted3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Delighted API to your scenario, reusing the same connection, for whatever the five other modules do not cover. You write the request yourself, and Make handles authentication with your key.

When to use it
a Delighted feature you need has no dedicated module in this list.
Watch out
this module expects you to read the Delighted API documentation to build the request; prefer a dedicated module whenever one exists.
Delighted4

Send to People

Action

In Make“Creates or updates a person and schedules a survey email.”

Adds a person to Delighted, or updates them if they already exist, and schedules a survey email for them in one step. That is how an event elsewhere turns into a survey without a manual import.

When to use it
a support ticket is closed, an order is delivered or a trial ends, and you want the customer's opinion on that moment.
Watch out
since it also updates existing people, check what you map into it so you do not overwrite good data with an empty value.
Delighted5

List People

Search

In Make“Returns a list of people.”

Returns the people stored in your Delighted account, each one as its own bundle, so the following modules can treat them one by one. It is the way to copy or audit your survey audience elsewhere.

When to use it
syncing Delighted contacts into a spreadsheet or a CRM, or comparing them with another list.
Watch out
as a search it can return zero, one or many people, and every module after it runs once per person, which adds operations.
Need help

Need help automating Delighted with Make?

A person reads every message.

FAQ

Delighted and Make: frequent questions

01Is the Delighted Make integration free?
Yes, Delighted is a standard app in Make, available from 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 (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations each month. Your Delighted subscription is separate and not covered here.
02What do you need to connect Delighted to Make?
Only your Delighted API key. Log in to Delighted, open Integrations then API, and copy the key. In Make, add a Delighted module, click Create a connection, give the connection a name, paste the key in the API Key field and click Continue. The Delighted documentation lists no other prerequisite. The same connection then works for all 6 Delighted modules, so you set it up once per account. Once it exists, Make lists your Delighted data in each module you add.
03Does the Delighted trigger in Make fire in real time?
Yes. Watch Survey Responses is an instant trigger: Delighted calls Make through a webhook as soon as a response is submitted, rather than Make checking on a schedule. The scenario has to be switched on to receive those calls. The 15 minute default schedule of Make applies to scheduled triggers, not to this one. The other five Delighted modules are actions or a search, so they run after a trigger.
04What if a Delighted module you need is missing in Make?
Use Make an API Call. It sends any request to the Delighted API with the connection you already have, so a feature without a dedicated module is still reachable. You build the request from the Delighted API documentation. The Delighted documentation gives no numeric limit for these modules, so the main constraint is the plan you are on in Make: scenario count, interval and execution time. If a request fails, check the connection first, since every module shares it.
05Should you pick Make or n8n for Delighted?
It depends on the tool your team already uses. On Make, Delighted comes with 6 ready modules, including an instant trigger on survey responses and Make an API Call for the rest of the API. Delighted may also exist as an n8n node; if your other automations already live in n8n, keeping them together is simpler. Compare the modules each side offers for what you need to automate, then choose.
Same platform

Other docs you might need on this stack.

Browse all integrations