Replacing Double Opt-In System Workflow

System workflows and events make usage of the platform more convenient. For example, Yespo widgets have a subscription confirmation workflow attached by default. When creating a form, it is enough to activate the switcher so that all new contacts who fill out the form on the site receive an email with a link to confirm the subscription.

Widget settings with the Double Opt-In toggle switched on, and an Email confirmation panel showing the default subscription confirmation email with Edit and Replace buttons

The built-in system workflow sends one confirmation email, specified in the widget settings, no more than once every 72 hours.

Custom DOI workflow diagram with a Send obligatory (transactional) email task connected between Start/Stop configuration and End

In some cases, you may need to change the system workflow: for example, send one or more messages asking to confirm the subscription to those who did not do this in the first email.

System workflow replacement algorithm:

  1. Setting up the subscription confirmation link in the email.
  2. Creating a workflow.
  3. Configuring trigger.
📘

Note

If you replace the system workflow, the new mailing scheme will be applied to all widgets in the account, while the emails can still be unique for each form.

Setting Up a Confirmation Link in an Email

The button with the confirmation link in the email for widgets should have the following settings:

Link:

  • Type: Subscription confirmation,
  • Link: $data.get('redirectUrl')
Email editor Button block settings with the Link type set to Subscription confirmation and the link value set to $data.get('redirectUrl')

Event type: SysContactConfirmed

Email editor Button block settings with the Event type set to SysContactConfirmed

Creating Workflow

Create a new workflow. It will be triggered by the SysContactConfirmationRequest system event, which is sent to Yespo when a user submits data from a widget on the site.

For example, if you want to remind about subscription confirmation three times with an interval of an hour, the workflow will be as follows:

Custom DOI workflow diagram with three Send obligatory (transactional) email tasks connected by 1-hour timers and Contact confirmed conditions branching to Yes or No

Workflow blocks:

  1. Start.
  2. The Send obligatory (transactional) email task with the following settings:
  • Contact’s email: specify the ${email} variable — the system will substitute from the event the email of the user who filled out the form.
  • Message: specify the ${messageId} variable — the system will substitute from the event the message specified in the settings of the widget that the user filled out.
Send obligatory (transactional) email task settings with the Message set to Confirmation email and the Email field set to ${emailAddress}
  1. Timer: specify the time to elapse between subscription checks.
Timer block settings with Wait time enabled and set to 1 hour
  1. The Contact confirmed condition checks if the user has confirmed their email: if yes, the workflow ends; if not, sends the message again.
Contact confirmed condition settings highlighted in the workflow diagram with the condition name set to Contact confirmed
  1. End.

After making the settings in the workflow blocks, save it and go to the launch settings.

Configuring Trigger

  1. Click Trigger configuration in the list of workflows.
  2. Activate the Start configuration switcher.
  3. In the Start configuration, select:
  • Event-based;
  • SysContactConfirmationRequest event;
  • arbitrary conditions for processing unique events.
Start/Stop configuration with Event-based selected, the SysContactConfirmationRequest event chosen, and Once in every 72 hours selected for processing repeated events
  1. Click Apply.

Learn more about events >

Once you activate the workflow, the system will apply it to all widgets in your account.


Did this page help you?