Sending a Follow-Up Survey from a Workflow

A Follow-up step emails the respondent a link to another survey — for example, inviting everyone who gave a low score to tell you more.

[Screenshot: The Follow-up survey panel with a survey chosen and a short message]

Before you start

The email goes to the address the respondent was originally invited from, so the trigger survey needs to be sent by email invitation from a contact list. Responses with no email address, such as those from an anonymous web link, can't be followed up and stop with the reason "The respondent has no email address to send a follow-up to". The follow-up survey itself needs an open web link collector, because that is the link the workflow sends.

Add a Follow-up step

  1. Click + where you want the step and choose Follow-up.
  2. Under Survey, choose the survey to send.
  3. If the survey has survey variables, enter a value for any you want to pass along the link under Survey variables. Variables marked Required by the survey should be given a value.
  4. Optionally write a Message (optional) to show above the link, with basic formatting and inserted response data if you like.
  5. Click Save step.

Only the survey is required (though note step 3 about required variables). Variable values can be fixed text or inserted response data; a value that works out blank is left off the link, and if the follow-up survey has secure variable links enabled the values are encrypted into the link. A variable the survey no longer defines is flagged in the panel — clear it to drop it. See Inserting Response Data into Workflow Actions.

How the email is sent

The email has the subject "You're invited to take a survey" and contains your message followed by the survey link. It counts towards your account's email balance. Any follow-up that couldn't be sent appears on the Issues page with the reason. See Monitoring Workflow Runs and Fixing Issues.

[CONFIRM BEFORE PUBLISHING: the From dropdown currently offers only the platform no-reply address (listSenderEmails is a stub pending the backend sender endpoint), and the send path always uses the site no-reply sender. Reword or remove step 2 once the sender feature lands.]

Was this guide helpful?