# Formbricks AI integration on Definable

> Formbricks is an open-source platform for building and managing surveys, enabling organizations to collect and analyze user feedback effectively.

## What this connects

Formbricks is an open-source platform for building and managing surveys, enabling organizations to collect and analyze user feedback effectively.

Vendor: https://formbricks.com

## Tools available

**45** tools available. First 12:

- `FORMBRICKS_CHECK_HEALTH` — Check Health — Tool to check the health status of the Formbricks API. Use when you need to verify that the API is operational and responding to requests.
- `FORMBRICKS_CREATE_ACTION_CLASS` — Create Action Class — Tool to create a new action class. Use when defining custom action logic in your environment.
- `FORMBRICKS_CREATE_ATTRIBUTE_CLASS` — Create Attribute Class — Creates a new attribute class (custom contact attribute) in Formbricks. Attribute classes define the schema for contact attributes used for segmentation and personalization. Each attribute must have a unique key within the environment. Common examples include 'plan', 'tier', 'company', or custom business-specific attributes. Use this when you need to define new contact attribute types before tracking user data.
- `FORMBRICKS_CREATE_CLIENT_USER` — Create Client User — Tool to create or identify a user within a specified environment. If the user already exists, this will identify them and potentially update user attributes. If they don't exist, it will create a new user. Use when you need to register or update users in the client API for survey targeting.
- `FORMBRICKS_CREATE_CONTACT` — Create Contact — Creates a new contact in a Formbricks environment. A contact represents a person or entity tracked in Formbricks for survey responses and interactions. The email serves as the unique identifier within an environment - if a contact with the same email already exists, this will update the existing contact. Use this action when you need to: - Register a new contact for survey distribution - Add contact information before sending surveys - Create or update contact records with custom attributes Prerequisites: - An environment ID (use GET_ME to retrieve available environments) - All attribute keys must exist in the environment (email is always available) - Write permissions on the API key
- `FORMBRICKS_CREATE_DISPLAY` — Create Display — Create a display record to track when a survey is shown to users. Displays are used to measure survey view counts and can optionally be linked to a specific user. Use this after obtaining valid survey and environment IDs to register that a survey was displayed.
- `FORMBRICKS_CREATE_RESPONSE` — Create Survey Response — Tool to create a response for a survey. Use after collecting all survey answers.
- `FORMBRICKS_CREATE_SURVEY` — Create Survey — Tool to create a new survey. Use after defining survey details and questions.
- `FORMBRICKS_CREATE_WEBHOOK` — Create Webhook — Tool to create a new webhook. Use when you need to register an external endpoint to receive form response events.
- `FORMBRICKS_DELETE_ATTRIBUTE_CLASS` — Delete Attribute Class — Tool to delete an attribute class. Use when you need to remove an attribute class by its ID after confirming it's no longer needed.
- `FORMBRICKS_DELETE_PERSON` — Delete Person — Tool to delete a person. Use when you need to remove a person's record from Formbricks after confirming the ID.
- `FORMBRICKS_DELETE_RESPONSE` — Delete Survey Response — Tool to delete a survey response by its ID. Use when you need to remove an existing response after confirming its ID.

## Auth

Auth schemes: `API_KEY`.

## How agents use Formbricks

Inside a Definable workflow, Formbricks is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Formbricks** — the Researcher (GPT-5.5) pulls context from Formbricks (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Formbricks** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Formbricks (create record, post message, draft email).
- **Designer / Engineer → Distributor → Formbricks** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Formbricks (attach file, open PR comment, post status).

The Verifier checks every Formbricks call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- forms & surveys — https://definable.ai/apps/category/forms-&-surveys/

## Related

- HTML page: https://definable.ai/apps/formbricks/
- Same category (forms & surveys): https://definable.ai/apps/category/forms-&-surveys/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt