Skip to main content
The “Ask A Question via Email” action allows you to send questions to specified e-mail addresses with responses that you configure. This action then receives the responses and lets you reference the selected answers in later steps of your workflow.

Creating a Workflow using the Ask a question via Email Action

  1. In the Workflow Editor, click to open the Action panel and search for “Ask a question via Email” action. Alternatively, you can drag the action to the step.
  1. Enter the following parameters in your step.
While the user is waiting for a response, the Step output shows Workflow execution paused.The recipient receives an email with a question and possible answers. An answer is selected and the Workflow continues to run in accordance with the answer.
  1. The recipient will then receive the question to their Email.
  1. You can then navigate back to your workflow where you can find the response to your question in the output of your Workflow.

Ask a question via email using an SMTP server

This action works the exact same way as the Ask a question via E-mail however it allows you to Ask a question via E-mail using a SMTP Server
In order to use this action, you need to create a connection by navigating to the top-right hand corner of your Step, select “Connection required” and then select an existing connection or create a new connection by selecting Create new connection. Select the SMTP Server option and fill out all the necessary fields and then click create connection

Parameters

Including user info

When Include user info is enabled, Blink sends a separate, individually-addressed email to every address in To, Cc and Bcc. Each recipient gets their own answer link, so the Step’s output can show which recipient answered.
  • Recipient limit: at most 30 different recipients across To, Cc and Bcc combined. The Step fails if this limit is exceeded.
  • Cc and Bcc: each Cc and Bcc recipient receives their own direct copy of the email, rather than a shared copy visible to the other recipients.
Output format: with this option enabled, the Step’s output is JSON instead of the plain answer text:
If you enable this option on an existing workflow, update any conditions that compare the raw output (for example output == "Yes") to read output.status instead.
  • The user field is for display only and is not verified. Anyone with the answer link can edit it, so don’t use it to gate approvals or other authorization decisions.
  • If an address is a distribution list or group alias (for example soc@corp.com), every member shares the same answer link, and user.id shows the list address rather than the individual who answered.