Skip to content

Build a workflow

A workflow does a job for you when something happens, like emailing your team when a low score comes in. Workflows need the Team plan or above. On lower plans Workflows isn’t in the top bar. You need a role that can edit workflows: a Viewer can’t create or publish one.

If you’re connecting a workflow to your own systems, see Webhook steps in workflows.

  1. Sign in at app.surveyrock.com. You start on Home.

  2. Click Workflows in the top bar.

  3. Click the arrow beside Create Workflow, then Start from scratch.

    The Create Workflow button with its menu open, and Start from scratch outlined under Create from template.

The editor opens with a workflow called “Untitled Workflow”. To rename it, click the name at the top and type.

There are three other ways to start:

  • From a survey: open the survey and click Workflows in the top bar. A new workflow starts with that survey as its trigger.
  • From a template: click Create Workflow to open Workflow Templates, then choose one. If it needs details, a panel asks for them, and then it opens in the editor.
  • From a description: on Pro and Enterprise, click Describe it and say what you want to automate.

The trigger decides when the workflow runs.

  1. Click the Trigger card at the top. It says “Configuration required” until you set it. The Trigger Configuration panel opens.

  2. Choose a trigger type.

    The Trigger Configuration panel listing Response Submitted, Scheduled, Inbound Webhook, Distribution Event, Contact Event, Status Change and Theme Threshold.

  3. Fill in the settings. For Response Submitted, choose the Survey, or Any survey in the workspace. To run only for some responses, turn on Only fire when a condition is met.

  4. Click Save.

Trigger When it fires
Response Submitted A survey response is submitted
Scheduled On a repeating schedule. Team offers Daily, Weekly, Monthly and Yearly. Hourly and more often need Growth or above
Inbound Webhook Another system sends a request
Distribution Event An email campaign’s message is opened, clicked, bounced, marked as spam or unsubscribed from
Contact Event A contact is added to or removed from a list
Status Change A workflow or survey status changes
Theme Threshold A theme’s mention count crosses a threshold. Pro and above
  1. Click the + below the Trigger card.

  2. Choose Action. Delay waits before the next step. Condition (If/Else) and Loop need Growth or above.

  3. In Choose an Action, click the action you want.

    The Communication group of actions: Send Email, Send Slack Message, Send Webhook, and Send Teams Message and Send SMS marked Coming soon.

  4. Fill in the step. For Send Email, enter To and Subject, then write the message. Tags inserts details from the run, such as an answer.

  5. Click Save.

  6. To add another step, click the + below the last one. Steps run from top to bottom.

The editor saves your work as you go, but nothing runs until you publish.

Step Plan
Send Email, Send Webhook, Delay Team and above
Send Slack Message Team and above. Connect Slack from the step
Condition (If/Else), Loop, Survey Digest Growth and above
AI Workflow Step Pro and above
Zendesk Ticket, Freshdesk Ticket Pro and above. Connect the account in Workspace Settings first

The panel lists every action. A padlock means your plan doesn’t include it, and clicking it shows the upgrade options.

You need a trigger before you can test.

  1. Click Test at the top right. The Test Workflow panel opens.
  2. For a Response Submitted trigger, click Generate Sample to fill in Trigger Payload.
  3. Leave Mode on Simulate. It runs every step without sending real emails, Slack messages or webhooks.
  4. Click Run Test. Execution Results shows what each step did.

Live runs the workflow once for real. It lists what it will send, and nothing goes out until you confirm.

  1. Click Publish.

    The top of a published sample workflow: the Published badge, the Enabled switch turned on, the Publish and Test buttons, and the trigger and email step below.

The message says “Workflow published successfully.” The badge changes to Published, Enabled turns on and the workflow starts running.

  • To pause it: turn off Enabled.
  • To change it: edit the steps. The badge shows Unpublished changes, and the published version keeps running until you click Publish again. Discard changes goes back to the published version.
  • To see its runs: click History in the left menu. It’s available after the first publish.

You want your support team to hear about low scores. You start a workflow and choose Response Submitted. You pick your NPS survey, turn on Only fire when a condition is met, and set it to scores of 6 or below. You add Send Email with the team’s address in To, and use Tags to put the score in the message. You run it in Simulate, check Execution Results, and click Publish.

The page says “Workflow has validation errors.” The panel below the top bar lists each problem. Click one to go to that step. Two common ones are “A trigger must be configured before publishing.” and “At least one action step is required.”

Publish says a step “requires the Growth plan or higher.” The + menu offers Condition (If/Else) and Loop on Team, but they can’t be published there. Remove the step, or filter responses in the trigger with Only fire when a condition is met.

I can’t see Workflows. Your plan is below Team. Workflows are on the Team plan and above.

Test says “Configure a trigger before testing.” Set the Trigger card and click Save.

The workflow didn’t run. Check that it’s Published and Enabled, and that the trigger names the right survey. Then look in History. If you changed it since publishing, the changes aren’t live until you click Publish.

Hourly isn’t in the Frequency menu. Hourly and more frequent schedules need Growth or above.

An action says “Coming soon.” You can’t use that action yet.