Formbricks

Automate survey operations in Formbricks. Agents create and delete surveys, list and inspect responses, submit new responses, and read contacts to close the loop between feedback and action.

9 actions API key available

Formbricks website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A product launch checklist reaches the feedback step in FlowRunner

Create Survey builds the post-launch survey from the standard question set, a rating block plus an openText follow-up

The survey link goes out through the launch email and in-app message

List Responses sweeps submissions every few hours, separating finished responses from abandons

Each finished response syncs to the reporting sheet and the respondent's CRM record

Ratings at the bottom of the scale with written comments are collected into a digest

The product lead reads the digest and decides which complaints become roadmap items and which get a direct reply

The decisions post back to the launch channel with links to the underlying responses

What This Integration Enables

Formbricks is the survey platform for teams that want to own their feedback infrastructure: open source, self-hostable, with a Management API that treats surveys as objects you build and query, not pages you click together. That makes it the right substrate for orchestration. FlowRunner agents create surveys programmatically, sweep responses into the systems where decisions happen, submit responses to fire the Formbricks pipeline, and read the contact base to keep segments honest, against Formbricks Cloud or your own instance. - Launch link and in-app surveys as steps in a workflow, not manual builder sessions - Sync every response to CRM, spreadsheet, or warehouse as it arrives - Route low scores to a human while the respondent still cares - Import feedback from other channels via Create Response, triggering webhooks and follow-up emails - Run data-retention cleanups on surveys and responses with review - Read workspace contacts to enrich and segment your audience Because Formbricks self-hosts, the same workflows run unchanged whether your instance is Formbricks Cloud or a container in your own VPC, which matters to teams whose survey data cannot leave their infrastructure. The destructive end of the API is real either way: surveys delete with all their responses attached. That is where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate belongs, and where this connector puts it.

Without FlowRunner

Surveys built by hand, every time Each feedback request starts from a blank builder, so most launches ship without one

Responses checked when remembered Submissions accumulate unread until someone opens the dashboard days later

Feedback trapped in the tool Answers live in the survey platform while decisions happen in the CRM, the tracker, and the war room

With FlowRunner

Surveys as workflow steps Agents create the survey from your standard blocks the moment the launch checklist fires

Responses swept on a schedule Every submission is read, routed, and synced within hours of arriving

Feedback lands where work happens Answers flow to sheets, CRM records, and alert channels automatically

Use Case Scenarios

The launch feedback loop that always ships

Every release checklist includes a feedback step. The agent calls Create Survey with the team's standard block structure, waits for responses, and sweeps them with List Responses. Finished submissions append to [Google Sheets](/integrations/google-sheets) and update the respondent's record in [HubSpot](/integrations/hubspot). Bottom-scale ratings with comments alert the product channel in [Slack](/integrations/slack) with the verbatim text. No launch goes unmeasured because measuring is no longer optional effort.

Feedback from every channel, one pipeline

Support closes a ticket and asks one rating question in the reply. The answer comes back by email, and the agent calls Create Response to submit it against the CSAT survey, which fires Formbricks' own pipeline: webhooks, integrations, the follow-up email. Feedback collected in the product, in support, and at events all lands in one survey's response set, so Get Survey and List Responses give one honest read instead of four partial ones.

Retention hygiene on a self-hosted instance

A quarterly workflow reads List Surveys and flags surveys closed for more than a year. For each candidate, Get Survey pulls the configuration and List Responses counts what would be lost. The compliance owner reviews the list and names what gets archived to cold storage first. Only after export confirmation does Delete Survey run, with Delete Response handling the one-off erasure requests that arrive between sweeps. List Contacts closes the loop, verifying the contact base matches the retention policy.

Human-in-Loop Highlight

Delete Survey does not just remove a survey. It permanently deletes every response ever submitted to it, and Formbricks cannot bring any of it back. A retention agent that runs unsupervised is one wrong ID away from erasing a year of product feedback, so the deletion on this page is proposed, never assumed. The agent posts: "Survey 'Q1 Onboarding CSAT' has been closed for 14 months and holds 312 responses, 41 with written comments. Export completed to the archive bucket at 09:12. Delete from Formbricks?" The data owner confirms, and only then does the call execute. Create Response gets the same respect for the opposite reason: submitting a response fires webhooks and follow-up emails that reach a real person, so bulk imports get a human check on the mapping before the pipeline lights up.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

9 actions

Surveys

List Surveys Retrieves all surveys in the workspace with ID, name, type, status, and question structure. The discovery step before reading responses or proposing deletions.
Get Survey Retrieves a single survey's full configuration: questions, blocks, welcome and thank-you cards, and languages. Used to verify structure before mapping answers.
Create Survey Creates a survey from a name and an array of question objects, openText, rating, multipleChoiceSingle and more, with optional cards and settings. The step that makes surveys part of a workflow instead of a builder session.
Delete Survey Permanently deletes a survey and its responses. Cannot be undone, which is why it sits behind this page's human gate.

Responses

List Responses Retrieves a survey's responses with paging, each carrying answer data, finished status, and metadata. The sweep behind every sync and alert workflow.
Get Response Retrieves a single response by ID with full answer data, contact association, tags, and timestamps. The context pull before a human follow-up.
Create Response Submits a response to a survey, mapping question IDs to answers. Triggers the full Formbricks response pipeline: webhooks, integrations, follow-up emails.
Delete Response Permanently deletes a single response. Cannot be undone. The precision tool for erasure requests.

Contacts

List Contacts Retrieves the workspace's contacts with their attributes, paged. Used to enrich segments and reconcile the audience against the CRM.

Frequently Asked Questions

What can FlowRunner do with Formbricks?

FlowRunner agents can run List Surveys, Get Survey, and Create Survey in Formbricks, plus 6 more actions.

Does connecting Formbricks to FlowRunner require OAuth?

No. Formbricks connects to FlowRunner with an API key, no OAuth flow required.

Can Formbricks trigger a FlowRunner workflow automatically?

Formbricks doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Formbricks

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us