Resources · Zapier integration

Formbricks Zapier integrationAutomate Formbricks with Zapier.

The Formbricks Zapier integration gives you 3 triggers, 0 actions and 0 searches. All three are instant, so a survey answer reaches your other tools the moment it lands. Formbricks only sends; the work happens in the next app.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Formbricks Zapier integration actually does

Formbricks is an open-source survey platform you place along the customer journey. Hooked to Zapier, it becomes a starting point: every time someone opens, finishes or changes a response, Zapier hears about it right away and passes the answers to whatever app comes next. That is the whole job, and it is a useful one.

Three outcomes cover most setups. A contact record that knows what the person said: Response Finished feeds a CRM such as HubSpot only once the survey is complete. An early alert on drop-offs: Response Created fires after the first answer, so you see people who start and never finish. A row that stays current: Response Updated pushes edits to a sheet or a database, so nobody works from a stale copy.

Now the limits. Zapier has no action for Formbricks: no step can create a survey, add a contact or write a response back into it. There is no search either, so a Zap cannot look up an old response. Formbricks always sits in first position, and the second app does the writing.

Another catch: the three triggers overlap. One person filling one survey can set off Response Created, then Response Updated several times, then Response Finished. Pick the one that matches the moment you care about, or you pay for the same answer three times.

If you are weighing tools, the Formbricks Make integration page covers the same app on Make, and the Make vs Zapier comparison puts the two side by side.

Vocabulary

Zapier words, in plain English

Seven terms. Read them once and the rest of this page reads easily.

Zap
The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap. Here it is always something happening to a Formbricks response.
Action
What the Zap does after it starts: the step that writes, sends or moves something in another app for you.
Task
What Zapier counts on your plan: one action that completed successfully. Failed actions and triggers are not counted.
Instant vs polling trigger
Instant: the app calls Zapier the moment something happens. Polling: Zapier checks on a timer. Formbricks only has instant ones.
Filter
A gate between the response and the next app: only answers that meet your condition go through, the rest stop there without a trace.
Connection
Your Formbricks account linked to Zapier once, then reused by every Zap that starts from Formbricks.
Cost

What a Formbricks Zap costs you

Short version: the Formbricks side is free, and you pay for what the next app does.

  • Trigger cost0 tasks
  • Successful action1 task each
  • Free plan100 tasks a month, two steps per Zap
  • Premium appNo, works on the free plan

A trigger never costs a task, so Formbricks firing a hundred times bills nothing by itself. Each action that succeeds afterwards counts as one task, and an action that fails is not billed. Formbricks is not a premium app, so it runs on the free plan, which gives 100 tasks a month and unlimited Zaps. The catch is the two-step cap: one trigger, one action. Add a filter or a second action and you have a multi-step Zap, which needs a paid plan. The polling grid (15, 2, 1 and 1 minutes) does not apply here, since all three triggers are instant.

Connect

Connect Formbricks to Zapier in three steps

  1. 01

    Open the connections page

    In your Zapier account, go to Apps and click + Add connection. You need an existing Formbricks account first, plus access to the surveys you want to watch if someone else owns them.

  2. 02

    Pick Formbricks

    Type Formbricks in the search box of the dialog, select it, then click Add connection. A new tab then opens on the Formbricks side so you can sign in.

  3. 03

    Sign in and allow access

    Log in to Formbricks in that tab and grant Zapier access to the account. The connection then appears in your list, and every Zap that starts from Formbricks reuses it.

First Zap

Your first Zap: finished surveys into HubSpot

GoalSend every completed survey to HubSpot, but only when the answer shows a score worth a follow-up.

  1. 01

    Create the Zap

    Start a new Zap and pick Formbricks as the starting app, then choose Response Finished as the event. Select your connection and fill in the webhook name.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent responses from your account, so finish one test survey beforehand and pick it from the list.

  3. 03

    Add the filter

    Add a Filter step from the plus icon. Choose the answer you spotted in the test, a number rule, and your threshold. A text rule on a number never passes.

  4. 04

    Add the HubSpot step

    Add HubSpot as the action, map the email and the answers from the Formbricks response into the contact fields, then test the step and read what came back.

  5. 05

    Publish

    Click Publish to switch it on. With the filter, this is a multi-step Zap, so it runs on a paid plan. On the free plan, drop the filter.

Triggers

The three Formbricks triggers

3 events start a Zap when something happens in Formbricks, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Response Created

Instant trigger

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

This one starts the Zap as soon as a person begins a survey. In practice that means after the first question gets an answer, long before they reach the end, so the data you receive is often partial.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want to know who opened your onboarding survey, including people who quit halfway.
Watch out
the webhook name is mandatory, and later answers will not arrive with this first delivery, so do not map fields that only appear at the end.
2

Response Finished

Instant trigger

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

Fires once Formbricks marks a response as finished, which makes it the cleanest moment to read a complete set of answers. If you only build one Formbricks Zap, it is usually this one.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
push a finished NPS answer into your CRM or a support queue, with every question filled in.
Watch out
people who abandon the survey never reach this state, so they never start the Zap. Pair it with Response Created if drop-offs matter to you.
3

Response Updated

Instant trigger

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

Runs whenever an existing response changes inside a survey. One response can change more than once, so the same person may set it off several times for a single survey.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep a spreadsheet row in step with a response that keeps changing, rather than adding a fresh row each time.
Watch out
every firing that reaches a successful action costs a task, so a response edited often can eat your monthly count faster than you expect. A webhook name is required here too.
When it breaks

When a Formbricks Zap breaks

Zapier lists no help article and no rate limit specific to Formbricks. What breaks is general Zapier behavior, and four cases cover it.

Most problems come from timing or from repeat firings, not from the connection. If a Zap keeps failing after you have checked these four, the Zapier troubleshooting page is the next stop.

  • Old responses never show up

    A Zap only reacts to what happens after you switch it on. Responses collected before that stay where they are; moving the backlog is a separate job.

  • A sudden flood gets held back

    If a burst of responses arrives at once, after an import or a migration, Zapier's flood protection can hold the batch back instead of running everything in one go.

  • The same person triggers three Zaps

    Created, Updated and Finished can all fire for one survey. Build on several of them and one answer turns into several runs and several tasks.

  • A Zap that feeds itself

    If a later step writes back into the very place a trigger watches, the Zap sets itself off again and again and burns through your task count.
Need help

Need help automating Formbricks with Zapier?

A person reads every message.

FAQ

Formbricks Zapier integration: common questions

01Is the Formbricks Zapier integration free?
Yes, it works on the free plan, because Formbricks is not a premium app. The free plan gives you 100 tasks a month and as many Zaps as you like. The limit to keep in mind is the two-step cap: one trigger and one action per Zap. As soon as you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. Since Formbricks only offers triggers, a simple two-step Zap that forwards responses to one app fits the free plan without trouble.
02How many tasks does a Formbricks Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that sends a finished response to one app uses one task per response. Add a second action and it doubles. An action that fails is not counted. Where people get caught is Response Updated: it can fire several times while one person fills in one survey, and each firing that reaches a successful action is billed. If you only need the final answers, Response Finished keeps the count down to one run per completed survey.
03Does Formbricks send responses to Zapier in real time?
Yes. All three Formbricks triggers are instant: the app tells Zapier as soon as the event happens, and the Zap starts right away whatever your plan. The polling interval of 15 minutes on the free plan does not apply, because Zapier never has to check Formbricks on a timer. In the editor, a Zap built on an instant trigger shows a lightning bolt. Keep in mind that instant only means fast delivery; Response Created still arrives after the first answer, before the rest of the survey exists.
04What is required to connect a Formbricks account?
An existing Formbricks account, and access to any survey owned by someone else that the Zap should watch. On the Zapier side, you open Apps, click + Add connection, pick Formbricks, sign in on the tab that opens and grant access. The connection is then reused by every Formbricks Zap. When you set up a trigger, you also have to fill in a webhook name, which is a required field on all three triggers. A clear name makes it easier to tell several Zaps apart later.
05Why does one survey start the same Zap several times?
Because each trigger watches a different moment, and one response passes through all of them. Response Created fires after the first answer, Response Updated fires on each change, and Response Finished fires at the end. If you have a Zap on each, or if you built on Response Updated, a single survey can produce several runs and several tasks. The fix is to choose one trigger per goal. For complete answers, Response Finished is the one that fires once per finished survey.
06What if the Formbricks operation you want is not available?
Then Zapier cannot do it directly with Formbricks today. The integration has three triggers and no action or search, so creating a survey, adding a contact or writing into a response from a Zap is not possible. The practical route is to let Formbricks start the Zap and have the next app do the writing, such as a CRM, a sheet or a messaging tool. If writing back into Formbricks is essential, that need belongs on the list when you compare automation tools.
07Zapier, Make or n8n for Formbricks?
Judge it on what your workflow needs from Formbricks. On Zapier, Formbricks offers three instant triggers and nothing else, so it fits when Formbricks is only the starting point and responses must flow out quickly. The free plan covers a two-step Zap, with 100 tasks a month. It does not fit if you need to create or change anything inside Formbricks, since no action exists here. Check those same criteria, starting points versus write-backs and the cost per run, on any other tool before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations