Resources · Make integration

Formbricks Make integrationAutomate Formbricks with Make.

Every Formbricks survey answer can start an automation the moment it lands. The Formbricks Make integration gives you 3 instant triggers and 1 API call module. This guide shows product and research teams how to connect the account and build a first working scenario.

Try the Formbricks integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Formbricks Make integration do for you?

The Formbricks Make integration links your Formbricks surveys to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, acts or searches. Here, Formbricks tells Make about survey responses as they happen, and Make runs the steps you chose next.

Catch complete answers only. Watch Response Finished fires when a respondent reaches the end of a survey. It is the natural start for anything that needs the full answer set, such as scoring feedback or handing a lead to sales.

Hear about a response from its first answer. Watch Response Created starts as soon as a new response exists, which usually means the first question got answered. Useful when a partial answer already matters, for example a low rating on the opening question.

Keep your copy in sync. Watch Response Updated fires when an existing response changes, so the record you keep elsewhere can follow. And when you need something none of these cover, Make an API Call reaches the Formbricks API with the same connection.

Make itself is candid about one limit: its Formbricks documentation is incomplete because little public information exists about the app. Expect to test with Run once to discover what each module sends. If you want a broader view of the tool first, read our Make review; to weigh it against the other big option, see n8n vs Make. Teams that prefer to hand the build over can talk to our Make agency.

Connect

How do you connect Formbricks to Make?

  1. 01

    Add a Formbricks module

    In your scenario, click the + and search for Formbricks. Pick any of its modules, then click Create a connection. A connection is your Formbricks account linked to Make once and reused by every Formbricks module afterwards.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps later. If you link more than one Formbricks account, a clear name tells you at a glance which account a module is using.

  3. 03

    Authorize and save

    Follow what Make asks for: either approve access on the Formbricks page that opens, or paste the key Formbricks gives you. Then click Save, and the connection is ready for every Formbricks module.

First scenario

Your first scenario with Formbricks

GoalWhen a respondent finishes a Formbricks survey, Make receives the full response and calls the Formbricks API for the next step you choose.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module. This first module decides when the whole automation starts.

  2. 02

    Pick Watch Response Finished

    Search for Formbricks, choose Watch Response Finished and create your connection. Since this trigger is instant, Formbricks will call Make through a webhook each time someone completes the survey.

  3. 03

    Add the API call

    Click the + on the right of the trigger and add Make an API Call from Formbricks. It reuses the same connection. Choose the endpoint from the Formbricks API reference and map fields from the finished response.

  4. 04

    Test with Run once

    Click Run once, then submit a test answer in Formbricks. Open each module to read the bundle it received, meaning the single response that traveled through the scenario.

  5. 05

    Switch it on

    When the test looks right, turn the scenario on. Every completed survey now runs it, and each module execution counts as one operation on your Make plan.

Triggers

What triggers a Formbricks scenario?

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

Formbricks1Watch Response Created

Watch Response Created

Instant trigger

In Make“Triggers when a new response is created for the survey. Normally triggered when the first question is answered.”

You learn about a new respondent almost as soon as they start, because this trigger fires when Formbricks creates a response, which normally happens once the first question is answered. The data may still be partial at that point.

How it fires
instant, Formbricks calls Make through a webhook as soon as it happens.
When to use it
a first question that asks for a satisfaction score, where a poor score should alert the support team before the rest is filled in.
Watch out
people who drop off halfway still create a response, so do not treat this as a completed submission.
Formbricks2Watch Response Finished

Watch Response Finished

Instant trigger

In Make“Triggers when a response is marked as finished.”

Only complete submissions reach your scenario with this trigger: it fires when Formbricks marks a response as finished. That makes it the safest starting point for most automations built on survey data.

How it fires
instant, Formbricks calls Make through a webhook as soon as it happens.
When to use it
an onboarding questionnaire whose answers should land in your CRM or project tool only once the respondent has gone through every question.
Watch out
respondents who leave before the end never reach this trigger; add Watch Response Created in a separate scenario if abandoned answers also matter to you.
Formbricks3Watch Response Updated

Watch Response Updated

Instant trigger

In Make“Triggers when a response is updated within a survey.”

Changes to a response inside a survey come through here, so the copy you keep in another tool never drifts from what Formbricks holds. It is the trigger that keeps a second system honest.

How it fires
instant, Formbricks calls Make through a webhook as soon as it happens.
When to use it
a multi-step survey where respondents keep adding answers, and a spreadsheet row that should grow with them.
Watch out
one response can fire this trigger several times, and each run costs operations; update the existing record instead of creating a new one every time.
Modules

What else can Make do in Formbricks?

Formbricks gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Formbricks1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module opens the whole Formbricks API to your scenario, using the connection you already created, so you are not limited to the three triggers. You pick the endpoint and send the request yourself.

When to use it
you need an action on Formbricks that no dedicated module offers, right after a response arrives.
Watch out
Make documents little about Formbricks, so keep the Formbricks API reference open and test every call with Run once before switching the scenario on.
Need help

Need help automating Formbricks with Make?

A person reads every message.

FAQ

Formbricks and Make: common questions

01Is the Formbricks Make integration free?
Yes, Formbricks is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Scheduled scenarios there run at most every 15 minutes, although Formbricks triggers are instant and do not wait for a schedule. Paid plans (Core, Pro, Teams and Enterprise) remove the active scenario cap and allow runs of up to 40 minutes. Usage is counted in operations each month.
02What do you need to connect Formbricks to Make?
A Formbricks account and a Make account. Make's documentation lists no specific prerequisite for Formbricks and gives no dedicated connection steps, so the standard flow applies. Add a Formbricks module, click Create a connection, optionally name it, then either authorize Make on the Formbricks page or paste the key Formbricks provides, and click Save. The connection is then shared by every Formbricks module in your scenarios. If a module later fails to read your surveys, check this connection first.
03Do Formbricks triggers in Make fire in real time?
Yes. All three Formbricks triggers are instant: Watch Response Created, Watch Response Finished and Watch Response Updated. Formbricks calls Make through a webhook as soon as the event happens, so your scenario does not wait for the 15 minute default schedule that applies to scheduled triggers. In the editor, these modules carry a lightning badge instead of a clock. Pick Created for the first answer, Finished for complete submissions and Updated for later changes.
04What if the Formbricks module you need is missing in Make?
Use Make an API Call. Formbricks has this module in Make, and it can call any endpoint of the Formbricks API with the connection you already set up. You choose the endpoint and build the request from the Formbricks API reference. Keep in mind that Make describes its Formbricks documentation as limited, due to little public information about the app, so rely on Run once tests to see exactly what each call returns before going live.
05Should you use Make or n8n for Formbricks?
It depends on which tool your team already runs. On Make, Formbricks offers three instant triggers on survey responses and an API call module, with a visual editor and a Free plan to start. The same app often has an n8n node too, so check the n8n side for the modules you need before choosing. Compare on concrete criteria: the events you must catch, the actions you need, and where the rest of your automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations