Workflows are part of the Formbricks Enterprise Edition.
How Workflows work
Trigger
The event that starts a workflow. The currently available trigger is Response completed for a
survey linked to the workflow.
Condition or filter
A rule that gates execution. You can currently filter completed responses by the ending card the respondent
reached.
Action
What the workflow does after its trigger and filter match. The currently available action is Send email.
Run
A concrete execution of an enabled workflow. Every run records its overall status and logs for its
individual steps.
Response completed trigger → optional ending card filter → Send email action
Available triggers, conditions, and actions
The builder lists the options available in your Formbricks version. The tables below show what you can use today.Triggers
Conditions
Actions
Current capabilities
You can currently use Workflows to:- Start when a response is completed for a selected survey
- Run for all ending cards or only selected ending cards
- Send a personalized email using survey response data
- Inspect workspace-wide or workflow-specific execution history
The available options currently include the Response completed trigger, its optional ending card filter,
and the Send email action. User-authored condition nodes, branching, webhooks, schedules, delays, and
loops are not available yet.
Get started
Build a workflow
Choose a trigger and action, configure them, optionally validate the workflow, and enable it.
Manage and monitor
Manage the workflow lifecycle and investigate runs and step logs.
Self-host Workflows
Self-hosted deployments run Workflows through the shared Redis-backed Job Runner built into the Formbricks web process. Before using Workflows in production, configure Redis and any services required by your actions, such as SMTP for Send email.Configure the Job Runner
Set up the runner, scale it across replicas, and troubleshoot queued or failed runs.