Skip to content
PynPyn

By use case

Run a pulse survey or poll

One question lands in a message every week or month, the click is the answer, and the results export as a CSV with one row per person. For: Power Users, admins and owners. Time: about 20 minutes.

The Weekly pulse check automation with its step open on the right: the Configure tab shows the email with the pulse poll embedded as Embedded Form: Answer the pulse under two lines of text.
The pulse step open: a weekly Recurring Trigger sends one message with the poll embedded, so people answer in a click.
  • A Power User, Admin or Owner role to create and publish the poll; an Admin or Owner to publish the automation; see Publish an automation.
  • An email sender, or Slack connected for direct messages; see Add an email sender and Slack.
  • The question. A poll is answered in one click, so keep it to one Likert Scale or one Checkbox; three to five questions make a form instead; see Polls and Forms.
  • A group for the audience if the pulse is for one team or country; see Create a filter group.
  • Optional: a Slack channel for a team-wide pulse, for a Post to Channel step, where enabled for your workspace.
  1. Create the poll under Flows, Polls with one Likert Scale field, the question in Label and Description left empty, then Preview and Publish; see Run a quick poll.

  2. For more than one question, build and publish a form with Required on the fields that matter instead; see Build a form.

  3. Create an automation with the Recurring Trigger under Dates and Schedules, set the start date, the time, the time zone and Weekly or Monthly, and check the list of upcoming runs; see Configure a recurring trigger.

  4. Open the trigger’s Audience tab, keep Lifecycle at Current and include the group the pulse is for, before you publish; see Set the audience for an automation.

  5. Add a Send Direct Message or Send Email to Employee step to Employee on the day of, write two lines on why you are asking, then select Insert widget, Embed Form and pick the poll or form; see Embed a form in a message.

  6. Select Preview, pick an employee under Preview for principal, then Send a test to yourself and click an answer; see Preview and send a test.

  7. Select Publish on the automation; see Publish an automation.

  8. After the first run, open the Activity drawer on the poll or form to read who has answered and select Export to CSV for the scores; see Review and export submissions.

The buttons sit under the message and the clicked one highlights. Each field can be clicked, so a form with a Likert scale and a checkbox works here. A click in Slack leaves the delivery Unactioned, so the export, not Actions, is the record of who answered. For a team-wide pulse, embed the poll in a Post to Channel step, where enabled for your workspace; see Post to a channel.

For a one-off pulse at a moment in the journey, skip the recurring trigger and put the same step at the end of week one in your onboarding automation; that is the flow Run a quick poll builds.

  • A recurring trigger with the default audience enrols every current employee on every run, so set the audience first. A 09:00 run enrols within the hour after 09:00; see Configure a recurring trigger.
  • A field’s Description replaces its Label as the question people see and as the CSV column header, so put the question in one or the other; see Form field types.
  • A Slack answer never changes the delivery status, so reminders on a poll step reach people who have already answered. Leave reminders off a poll; see Add reminders.
  • Your own test clicks are excluded from the Activity drawer and the export, and the export stops at 1,000 rows; see Review and export submissions.
  • Unpublished polls appear in the Embed Form list, so publish before the step sends, and again after any later edit; see Build a form.

After the first run, Enrollments lists one enrollment per audience member with the run date as Reference Date, and each later run adds another set. The step reads Delivered, then Actioned once the person opens the poll from an email. In the poll’s Activity drawer each answer sits against the person’s name, newest first, and the CSV holds employeeId, submissionId and the Likert score as a number from 1 to 5. Under Actions, filter by the step for who has not opened an email poll; see Track actions.