Skip to content
Workflows

Chain outreach using previous trigger history

Show a follow-up only after an earlier supported interaction has occurred.

CCorthex product guidesUpdated October 15, 20262 min read
Where to find itWorkflow builder → history conditions

Before you begin

Open Workflows in the workspace navigation. Decide which event should start the flow and which agents should receive it. Start with an unpublished draft.

Example workspace · Demo data. 1 — Conditions decide whether the action path is eligible. Select the image to enlarge it.
Workflow branch inspector with page condition and all/any match controls

Example workspace · Demo data. 1 — Conditions decide whether the action path is eligible. Select the image to enlarge it.

Step by step

  1. 1

    Name the stages clearly

    Define the first invitation and the follow-up outcome. Keep their identifiers and purpose distinct.

  2. 2

    Use a history condition

    Choose the supported prior-trigger/shown history field and reference the intended earlier event. Shown is different from clicked or completed.

  3. 3

    Add the current context

    Combine the history with the new page or conversation condition. Add repeat/frequency controls where available.

  4. 4

    Test fresh and returning sessions

    Verify a new visitor does not skip ahead, and a visitor with the intended earlier event can qualify. Also test dismissal and reset/new-session behavior.

Good to know

Browser/session history is not a permanent identity record across every device. Match the actual scope exposed by the condition.

Check the result

Test matching, non-matching and missing-data cases. Review the publication, publish the steps and save the intended agent assignments.

Questions & troubleshooting

The follow-up never appears

Check that the previous event was recorded in the same supported scope, and that the current event causes evaluation again.

Was this article helpful?

Rate this guide on this device. Ratings are not sent to Corthex.