Can multiple workflows run at once?
Yes. A single widget can have multiple active workflows. When a visitor opens the widget or performs an action, Yaplet checks all active workflows whose trigger and URL conditions match, and fires them according to priority rules.
How priority works
When multiple workflows match the same trigger at the same moment, the workflow with the earliest creation date takes priority. Only one workflow fires per trigger event on a given visitor session. The others stay in the queue for subsequent trigger events.
To change the effective priority, consider the order in which you create workflows — or use specific URL conditions to ensure only one workflow matches a given page.
Different workflows for different pages
The most common multi-workflow setup is page-specific targeting: one workflow fires on the pricing page, a different one fires on the documentation page, and a third fires on checkout. Because each workflow has its own URL condition, there's no conflict — only the matching one fires.
Full details on URL targeting: Target a workflow to specific pages.
Different trigger types don't conflict
A "Visit" workflow and a "Chat Open" workflow can both be active on the same page without conflict — they fire on different events. The "Visit" workflow fires when the page loads; the "Chat Open" workflow fires when the visitor clicks the widget launcher. Use this to layer experiences: a visit-triggered workflow runs silently in the background (collecting data, showing a banner), while a chat-open workflow runs when the visitor actively engages.
Frequency caps per visitor
Workflows with the "Visit" trigger include a frequency control: you set how often the same visitor can trigger the workflow (for example, once per session, or once every 30 minutes). This prevents a returning visitor from being greeted with the same intro workflow every time they open a new tab. Configure the frequency in the trigger settings of each workflow.
Debugging multi-workflow setups
If a workflow isn't firing when you expect it to:
- Check that the workflow is set to Active in Settings.
- Check the URL condition — it may be too strict or mistyped.
- Check the widget assignment — the workflow must be linked to the widget on that page.
- Check the frequency cap — the visitor may have already triggered the workflow recently and is in a cooldown period.
- Check whether a higher-priority workflow is consuming the trigger event.
Next step
Once your workflows are running, track how they perform: Read workflow analytics.