How to connect Formbricks to OpenClaw
Connect Formbricks to OpenClaw with ClawLink: paste your Formbricks key once and 45 tools work from chat. No MCP server to run, nothing stored on your machine.
FormbricksAPI KEYMCPFormbricks is an open-source platform for building and managing surveys, enabling organizations to collect and analyze user feedback effectively.. Once connected, OpenClaw can read and act on Formbricks from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Formbricks access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Formbricks setup: install one ClawHub skill, connect Formbricks in the browser, and OpenClaw can call real Formbricks actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Formbricks.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Formbricks
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Formbricks?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Formbricks in the ClawLink dashboard — paste your Formbricks API key once.
Verify the connection by asking OpenClaw:
Use Formbricks to check health and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Formbricks is connected in the dashboard, that agent calls the same 45 Formbricks tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Formbricks MCP for OpenClaw
Looking for a Formbricks MCP server for OpenClaw? ClawLink connects Formbricks to OpenClaw and exposes 45 Formbricks tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Formbricks integration works the same way.
What the OpenClaw Formbricks integration can do
45 Formbricks tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 45.
30 of 45 Formbricks tools for OpenClaw
| Tool | What it does |
|---|---|
Check health formbricks_check_health | Check the health status of the Formbricks API |
Get account info formbricks_get_account_info | Retrieves environment information for the authenticated API key |
Get all contacts formbricks_get_all_contacts | Retrieve all contacts within the organization |
Get attribute class formbricks_get_attribute_class | Get a specific attribute class by ID |
Get client contacts state formbricks_get_client_contacts_state | Get the current state of a contact including surveys and segment information |
Get contact attribute key formbricks_get_contact_attribute_key | Retrieve detailed information about a specific contact attribute key by ID (v2 API) |
Get contact by ID formbricks_get_contact_by_id | Retrieve a specific contact by its ID |
Get me formbricks_get_me | Retrieve current authenticated organization's and environment details |
Get person by ID formbricks_get_person_by_id | Retrieve a person by their internal ID in Formbricks |
Get responses formbricks_get_responses | Retrieve survey responses with flexible filtering, sorting, and pagination |
Get roles formbricks_get_roles | Retrieve all available roles in the system |
Get webhook formbricks_get_webhook | Retrieve details of a specific webhook |
List action classes formbricks_list_action_classes | List all action classes in your Formbricks environment |
List attribute classes formbricks_list_attribute_classes | List all attribute classes |
List client environment formbricks_list_client_environment | Retrieve environment state for Formbricks SDKs |
List contact attribute keys formbricks_list_contact_attribute_keys | Retrieve contact attribute keys from Formbricks |
List health formbricks_list_health | Check the health status of critical application dependencies including database and cache |
List management contact attributes formbricks_list_management_contact_attributes | Retrieve all contact attributes in the environment |
List management me formbricks_list_management_me | Retrieve authenticated user's environment and project information |
List management people formbricks_list_management_people | Retrieve all people (legacy term for contacts) in the environment |
List organization teams formbricks_list_organization_teams | Retrieve all teams in an organization (v2 API) |
List organizations project teams formbricks_list_organizations_project_teams | List all project-team assignments for an organization (v2 API only) |
List surveys formbricks_list_surveys | List all surveys in the environment |
List webhooks formbricks_list_webhooks | List all webhooks configured for the current environment |
Create action class formbricks_create_action_class | Create a new action class |
Create attribute class formbricks_create_attribute_class | Creates a new attribute class (custom contact attribute) in Formbricks |
Create client user formbricks_create_client_user | Create or identify a user within a specified environment |
Create contact formbricks_create_contact | Creates a new contact in a Formbricks environment |
Create display formbricks_create_display | Create a display record to track when a survey is shown to users |
Create response formbricks_create_response | Create a response for a survey |
Try it: find the Formbricks tool you need
Browse the 30 Formbricks tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Formbricks to check health and walk me through the result in plain English.
Pull the relevant data from Formbricks, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Formbricks, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Formbricks, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Formbricks working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Formbricks API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Formbricks account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Formbricks. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Formbricks actions to the runtime in a format your agent can reliably use. | 45 tools for Formbricks are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Formbricks to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Formbricks in the browser, and the 45 tools above work from chat. There is no SDK and no config file, and the Formbricks key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Formbricks skill but can't call the tools
The ClawHub skill teaches OpenClaw about Formbricks, but the calls run through the ClawLink plugin and your connected account. Make sure Formbricks is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Formbricks from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Formbricks tools
Formbricks tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Formbricks call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Formbricks returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Formbricks has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Formbricks integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Formbricks: link your Formbricks account once in the browser and OpenClaw can call the Formbricks API through 45 ready-made tools — no custom code or token handling.
How do I add Formbricks to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Formbricks skill from ClawHub, then you click Connect in the dashboard to authorize Formbricks. OpenClaw calls the tools from the next message — no config files, and the Formbricks key you paste is stored server-side instead of in your environment.
How long does it take to connect Formbricks to OpenClaw?
About two minutes. Sign in, click Connect next to Formbricks in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Formbricks up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Formbricks working from chat.
OpenClaw installed the Formbricks skill but can't call the tools
The ClawHub skill teaches OpenClaw about Formbricks, but the calls run through the ClawLink plugin and your connected account. Make sure Formbricks is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub tools
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.