Data & Storage · Integration
Formbricks
Add Formbricks to your product for your customers, and give your AI agents governed access to it.
Formbricks Cloud exposes its management API at app.formbricks.com/api/v1/management, authenticated with an x-api-key that is scoped to a single environment, so a key issued for a development environment will never see production surveys and the connection has to record which environment it belongs to. Response payloads store answers in a data object keyed by question id rather than question text, so you must fetch the survey definition and build the id-to-headline map yourself before anything is readable. Contacts carry free-form attributes whose keys are defined per environment, and targeting rules reference those keys, so writing an attribute that does not yet exist quietly creates a new one instead of failing. Webhooks for responseCreated and responseFinished are the practical way to keep up, because a partially answered survey is a real response record that later changes in place. Formbricks is open source and often self-hosted, so a customer connection may point at their own base URL rather than the Cloud host. fastn holds each customer's key and base URL, refreshes what needs refreshing, and keeps the environment scope attached to the tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Formbricks environment so in-app survey responses flow into your product without a CSV export.
Attach NPS and CSAT scores from finished responses to the right account record in your own reporting.
Create Formbricks contacts and set attributes from your user table so surveys target the correct cohort.
Show a customer's live surveys, response counts and completion rates inside your own dashboard.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Have an agent summarise open-text answers for one survey, with every read audited per tenant.
Let an agent flag responses containing churn language and raise a task for the account owner.
Ask an agent to report which questions are being skipped most often, with write access withheld.
Example prompt
Which questions in our onboarding survey have the highest drop-off this month?
Set up Formbricks in 4 steps
- 01Enable the Formbricks connector from your fastn dashboard.
- 02Have each customer authorise their own Formbricks account, so calls run under their credentials rather than a shared key.
- 03Decide which records, datasets and fields your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Formbricks integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Formbricks integration without building it. Your customers connect their own Formbricks account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Formbricks update is not your on-call problem.
- One integration serves your product and your agents. The same governed Formbricks connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Snowflake
Airtable
PostgreSQLOften used alongside
Tools the same teams tend to run next to Formbricks, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceFormbricks integration FAQ
How do I add a Formbricks integration to my product?
Enable the Formbricks connector in your fastn dashboard, then let each customer authenticate their own Formbricks account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Formbricks client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Formbricks account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Formbricks account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Formbricks integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Have an agent summarise open-text answers for one survey, with every read audited per tenant.
Who maintains the Formbricks integration?
fastn does. When Formbricks changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Formbricks integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Formbricks reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Formbricks integration?
A common starting point: let a customer connect their own Formbricks environment so in-app survey responses flow into your product without a CSV export. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Formbricks integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Formbricks does not change your per-connector cost. You can start free with 3 connected accounts.
Add Formbricks to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.