Skip to content

Area: User guide

How workflows work

A workflow is a multi-step automation drawn on a canvas: a Start step followed by messages, waits, conditions and splits, connected in the order they should run. Workflows live under Workflows in the left menu and share their list, editor tabs and status controls with Campaigns. The difference is the content: a campaign sends one e-mail or ad, a workflow runs a flow of steps across channels.

This page explains the parts; the guides show the clicks: Create a one-off workflow and Change the steps of a workflow.

Type Menu Who enters When it starts How it ends
One-off Workflows › One Off Everyone in the segment at launch When you select Launch (or at the scheduled date and time) When the last step has run
Continuous Workflows › Continuous Profiles that enter the segment while the workflow is on When you switch it On (optionally after a Delayed Start) At the End Date, or when you switch it Off
Triggered Workflows › Triggered A profile each time it performs a chosen event, or each time your system calls the workflow’s webhook When you switch it On When you switch it Off

A one-off evaluates its segment once; the Audience tab says so: The segment is evaluated at launch time. A continuous workflow re-evaluates its segment on Releva’s segment schedule and starts the flow for profiles that are new to it. A triggered workflow does not use a segment when it is triggered by an event; to narrow its audience, put a Condition step before the first message.

The Content tab shows the step palette on the left and the canvas on the right. Drag a step from the palette onto the canvas, then drag from the dot under one step to the top of the next to connect them. Only steps connected to Start run. Select a step to change its settings; press Delete to remove it; the × on a connection removes it.

Group Steps What they do
MESSAGES Email, Push, Viber, WhatsApp, Text Send a saved message. Each step has a message picker, a pencil to edit the message, Send on day circles and a moon for quiet hours.
ADS Facebook, Google (continuous only) Add the profiles to a Facebook ad audience (optionally with lookalikes) or a Google asset group with a membership duration.
LOGIC Wait, Condition, A/B split Wait pauses the path for a fixed number of hours; in triggered workflows it can also wait until a date in the triggering event (Dynamic (event date), with a merge tag and an offset in hours before it). Condition evaluates segment-style rules: drag from the green (left) dot for people who match the rules and from the red (right) dot for people who do not. A/B split sends half of the profiles down each path.
CUSTOM Webhook Call a saved webhook for each profile. See How webhooks work.

A workflow is saved with the steps you drew. The server rejects a flow with no steps, a flow whose steps form a loop (the message starts with We found a problem in your workflow. Some of your steps create a never-ending loop), and a message step with no Send on day enabled.

Campaign Scope on the Audience tab decides whose consent is checked:

  • Opt-in Marketing (default): only profiles that agreed to marketing on the channel.
  • Opt-out Marketing: every profile that has not unsubscribed on the channel, whether or not it opted in. Ask your account owner which scope your market allows.
  • Transactional: everyone, regardless of consent. Use it only for messages the customer expects, such as order confirmations. The form warns that misuse may break GDPR and other data protection laws.

Target Segment offers only Behavior segments. See How segments work and How consent works in Releva.

Continuous and triggered workflows have Repeat Entry on the Audience tab. With Allow users to enter this campaign multiple times off, each profile goes through the flow once. With it on, you set a Cooldown Period in days (up to 365; a continuous workflow needs at least 1) or, for triggered workflows only, in hours (3 to 24). A continuous workflow with a cooldown in hours cannot be saved. A profile that already entered is skipped until the cooldown since its last entry has passed. Releva keeps a record of each entry per profile and workflow to apply this rule.

Saving never sends anything. A workflow is a draft until you start it from the list:

  • One-off: the card shows Launch. Launching marks the workflow as running and queues the segment calculation, immediately or one hour before a scheduled start. The card then shows Scheduled or Running and an Abort button; aborting cannot be undone (If you abort now, you will not be able to resume it later.).
  • Continuous and triggered: the card has an On / Off switch. Switching on makes the workflow live; a continuous workflow with a future Delayed Start shows Launch instead and starts at that time.
  • Starting is blocked with Click tracking not ready - check Click Tracking settings while the shop’s click-tracking DNS record is not verified and the flow has a step that wraps links. Ads-only or webhook-only flows are not blocked.
  • Starting a workflow inside the shop’s quiet hours does not ask for confirmation. Each message step applies the quiet hours itself through its moon (see below).

While a workflow is running its steps are read-only. To change them, abort the workflow and select Make a copy.

A message step does not necessarily send the moment the path reaches it:

  • Send on restricts the step to the selected weekdays; a message that falls on another day moves to the next allowed day.
  • The moon (Observe quiet hours, on by default) holds the message until the shop’s quiet hours end. Send at Optimal Time on the Launch Configuration tab overrides quiet hours for the whole workflow and spreads sends over 24 hours.
  • A message whose daily limit is reached is rescheduled or skipped according to the message’s own On daily limit reached setting. See How emails work and How push notifications work.
  • Wait adds its hours to the path; the next step then applies its own rules.

Statistics on a card opens the results page with three tabs: Overview (the campaign metrics for the selected period), By channel (one row per message with Sent, Delivered, Opened, Clicks, Purchases, Revenue, Bounces, Complaints, Unsubscribes, Conversions) and By step (the same numbers per canvas step, as a table or on the flow). The Goal tab defines up to 3 goals (default Purchases, counting Cart Checkout Completed events with revenue tracking) that are reported in analytics.