AI agent integrationFormbricks

Formbricks integration for multiplayer collaboration with AI agents using Claude Code or Codex

One governed connection your whole team and its AI agents can share, with approved actions and human review, so working in Formbricks never means pasting credentials into a prompt.

Request access See API details

CategoryDocuments & Forms

Use Formbricks from Claude Code

Bring Formbricks context into engineering work while Type keeps app access attached to the teammate and workspace.

Automate Formbricks with Codex

Let coding agents ask for the right app action, preserve conversation context, and keep humans in the approval loop.

Connect open agent workflows

Use Type as the collaboration layer around OpenClaw and other LLM workflows that need app access.

Documents & Forms

What the Formbricks integration exposes

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

One connection, many teammates

Connect Formbricks once, then decide which teammates can use it for threads, automations, skills, and coding work.

Representative actions

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.
Create Action Class
Tool to create a new action class. Use when defining custom action logic in your environment.
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.
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.
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

Connection

API and auth details

Formbricks is an open-source experience-management and survey platform with API-first infrastructure. Public docs cover surveys, in-app feedback, link surveys, self-hosting, OpenAPI-backed endpoints, SDKs, webhooks, response streaming, and programmatic survey/resource management.

Source: Type catalog metadata
Auth schemes: API key
API docs: https://formbricks.com/docs/overview/what-is-formbricks
API reference: https://hub.formbricks.com/api
Auth docs: https://hub.formbricks.com/api
Official site: https://formbricks.com/

Source links

FAQ

Questions people ask before connecting Formbricks

Can Claude Code use Formbricks?

Yes. Type lets an AI teammate use connected Formbricks actions from a governed workspace context, so Claude Code work can reference the app without copying credentials into a local prompt.

Can Codex work with Formbricks through Type?

Yes. Codex can collaborate through Type with app context, skills, and approved actions. The Formbricks catalog entry includes public integration details and example capabilities where available.

Is this the same as a Formbricks MCP server?

Type exposes connected app capabilities to AI teammates and coding agents through Type's integration layer. Teams use it when they want shared app access, human review, and teammate-level permissions around agent work.