CSAT and survey triggers
Fire workflows the moment a contact answers your satisfaction (CSAT) survey and react based on the score.
Watch this step in the video · The palette: triggers and nodes
What it is and when to use it
The CSAT response received trigger (csat.received) starts a workflow the instant a contact answers your satisfaction survey. It's perfect for reacting in the moment: thank a customer who left 5 stars, open a conversation with someone who rated you low, or alert a supervisor when negative feedback comes in.
Requirements
- An active CSAT survey. Configure it under Settings → CSAT (name, question, scale of 1–5, 1–10, emoji or thumbs, send delay, and when it fires).
- Permission to create automations in the workspace.
Steps
- Go to Workflows in the side menu and click Create workflow (or open an existing one).
- In the left palette, under Triggers, pick CSAT response received.
- Open the trigger inspector and, if you want, narrow when it runs with the filters:
- Minimum score and Maximum score: for example, min 1 and max 2 to capture only detractors.
- Specific survey: if you run more than one survey, scope the workflow to a single one.
- Add the action nodes you need. You can use these event variables:
$csat.score— the score received.$csat.comment— the feedback text.$csat.survey_id— which survey was answered.$csat.responded_at— when they replied.- Conversation and contact variables (
$contact.name, etc.) are also available.
- Click Save and turn the workflow on with the toggle.
A practical example
Build two workflows with the same trigger:
- Promoters (minimum score 4): send a thank-you message and add the
happy-customertag. - Detractors (maximum score 2): assign the conversation to a supervisor and notify the team with
$csat.comment.
Verify it
Answer the survey yourself from a test number. In Workflows, open the workflow and check the runs tab: you should see an execution with the score captured in the variables.
If it doesn't work
- It never fires: confirm the survey is active and that the contact actually submitted a response (receiving the survey isn't enough).
- It filters too much: make sure the minimum/maximum score doesn't exclude the case you're testing.
- Wrong survey: if you run several, set the Specific survey filter to the correct ID.
- Workflow is paused: check the activation toggle.
Tips
- Leave the score unfiltered and branch with a condition node on
$csat.score: one workflow then handles both promoters and detractors. - Use
$csat.commentin internal notifications so the team can read feedback without opening the conversation.
Related articles
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Workflows complete guide
Workflows in depth, in 54 chapters: triggers, nodes, variables, testing, history, templates, import and export, with every setting explained and a real workflow end to end.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.