
Connectors / Customer service · HTTP Connector
Automate Formbricks with Tray.ai
Create a survey, create a response and create an action class in Formbricks, and start a workflow when Formbricks sends “Response created”.
Thanks — someone from our team will be in touch soon.
What can you do with Formbricks on Tray.ai?
Formbricks is an open source survey platform for running in-app, website, and link surveys and collecting user feedback, available as a cloud service or self-hosted. Tray.ai connects to Formbricks through the HTTP Connector, so your workflows can call the Formbricks API alongside the rest of your stack.
- When Formbricks sends “Response finished”, add the score and comments to the customer's record in your CRM.
- When Formbricks sends “Response created”, post low ratings to the product team's chat.
- Get single-use links from Formbricks and send one to each customer when their ticket closes in your help desk.
- Connects through
- HTTP Connector
- Authentication
- An API key in a request header
Set it up
Connect Formbricks to Tray.ai
Each step uses Formbricks's own API details, from its documentation.
Step 1
Save Formbricks's API key
Save the key as a Tray.ai authentication. The HTTP Client puts it in the request header, read from $.auth. The key stays out of the workflow and out of the logs.
Step 2
Import a request from Formbricks's docs
Add an HTTP Client step and paste a cURL example from Formbricks's API docs. Tray.ai fills in the method, URL, headers, and query.
Step 3
Start with “List surveys”
It's one of 18 documented actions, under Surveys. The response comes back as data the next step can map into your other apps.
Step 4
Start workflows from Formbricks events
Give Formbricks the URL of a Tray.ai webhook trigger. “Response created” can then start a workflow, and so can 2 other events.
What the Formbricks API covers
5 resources and 18 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.
Surveys
- List surveys
- Create a survey
- Update a survey
- Delete a survey
- Get single-use links
Responses
- List survey responses
- Create a response
- Update a response
- Delete a response
Contacts
- List contacts
- Get a contact
- List contact attributes
Action classes
- List action classes
- Create an action class
- Delete an action class
Webhooks
- List webhooks
- Create a webhook
- Get a webhook
Events Formbricks can send to a Tray.ai webhook trigger
- Response created
- Response updated
- Response finished
Checked against Formbricks's own documentation on 2026-10-22
How Tray.ai makes this work
Formbricks plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 6,000+ apps, databases, APIs, and services with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Formbricks — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose Formbricks actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on Formbricks data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More customer service apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every customer service connector →
Frequently asked questions
What can a Tray.ai workflow do in Formbricks?
+
The Formbricks API documents 18 actions across 5 resources (Surveys, Responses, Contacts, Action classes, Webhooks). For example: List surveys; List survey responses; List contacts. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with Formbricks?
+
The Formbricks API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.
Which Formbricks events can start a Tray.ai workflow?
+
Formbricks sends 3 events to a webhook URL, for example: Response created; Response updated; Response finished. A Tray.ai webhook trigger receives them and starts a workflow.
See Formbricks working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.