Skip to content
Workflows

Combine page, message, contact and history conditions

Express useful rules without accidentally matching every visitor.

CCorthex product guidesUpdated October 23, 20263 min read
Where to find itWorkflow builder → conditions / branches
In this article

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

    Choose the fields

    Select supported fields from the builder, such as page, message count, topic or prior trigger history. Read the operator and value together.

  2. 2

    Check verified-session availability

    The reserved user_logged_in, user_id, workspace_id, workspace_role and workspace_plan fields are supplied by the server only for customer-message workflows of Corthex’s own website assistant. They are absent on other agents, customer embeds and browser website events; storefront is_logged_in is a separate field. This does not add a general visitor identity integration to your widget.

  3. 3

    Set all/any logic

    Use all conditions when each requirement must hold. Use any only when one alternative should be enough. Review nested groups carefully.

  4. 4

    Handle missing values

    Test a visitor without a name, an empty conversation and a missing page URL. Do not assume missing data is the same as a negative answer.

  5. 5

    Check boundary values

    For a minimum message count, test just below, exactly at and above the threshold. For URLs, test query strings and nearby pages.

  6. 6

    Trace the branch

    Inspect the test result and selected branch. Use a clear fallback path when no branch qualifies.

Example
Example scenario — configure with the builder’s supported fields:
ALL conditions must match
  Page URL contains /installation
  Conversation message count meets your chosen threshold
  Topic matches installation support
THEN offer the relevant contact form or support route
ELSE continue the ordinary conversation

Examples of all, any and missing-data behavior

Use all when each requirement must hold: the visitor is on the installation page, has supplied enough conversation context and the topic matches installation support. Use any when each listed alternative independently qualifies, such as either of two explicitly selected pages.

Keep the fallback visible. A visitor without a page URL, a first message without a known topic or an empty custom field needs a defined outcome. Do not assume absence means false for every operator. Read the field’s available operators and inspect test inputs.

For counts, test below, at and above the threshold. For URL matching, test a nearby path, locale prefix and query string. For history rules, distinguish shown from clicked or completed and check the scope in which the event is recorded.

  • Positive case: all intended requirements are present.
  • Negative case: one decisive requirement is deliberately false.
  • Missing-data case: remove one field entirely.
  • Overlap case: two branches could qualify; verify priority.
  • Repeat case: cause the event again after an earlier invitation or form.

Good to know

Keep the first version readable. A few explicit conditions are easier to audit than a deeply nested rule that nobody can explain.

Use Verified website login equals true for signed-in guidance and an explicit equals false branch for guests. Check is set / is not set for unavailable fields; missing does not mean signed out. The four ID/workspace text fields are optional. Simulator values do not authenticate a real visitor.

Verified session fields route guidance, not grant account access. A name, typed ID, contact form or custom field cannot set them. Account changes and private data retain normal dashboard permissions.

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 rule matches too many people

Check all versus any, a broad contains operator and empty/default values.

Was this article helpful?

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