Skip to content
Workflows

Publish a workflow and assign it to agents

Understand drafts, published steps and workspace-wide agent assignments.

CCorthex product guidesUpdated October 15, 20262 min read
Where to find itWorkflows → Publish / assignments
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. Follow the path from starting event to decision and action. Select the image to enlarge it.
Workflow canvas with trigger, condition, actions and settings

Example workspace · Demo data. Follow the path from starting event to decision and action. Select the image to enlarge it.

Step by step

  1. 1

    Review the draft

    Check names, trigger, branch defaults, copy and required action configuration. Resolve validation errors.

  2. 2

    Publish the reviewed version

    Use Publish so the intended steps become the live version. Keep unfinished changes as drafts.

  3. 3

    Choose agents

    Select one or more agents in the assignment controls and save the assignments. Confirm the bot IDs match the websites/channels you intend.

  4. 4

    Verify the live result

    Cause the relevant event using one assigned agent and one unassigned agent. Confirm the latter is unaffected.

  5. 5

    Monitor the rollout

    Inspect run history and actual conversations before widening the assignment.

Check the three separate live-state controls

The editing draft, published steps and saved agent assignments have different jobs. Saving protects your configuration edits. Publishing selects the reviewed steps that should run. Assignments define which agents receive the live flow.

Before rollout, confirm the intended workspace and bot IDs, test representative scenarios, review the publication summary and save the assignments. Test one assigned agent and one unassigned agent so the scope is proven rather than assumed.

When reusing another workflow, check that its live target is enabled, published and assigned to the calling agents. A shared target change can affect more than one caller. Inspect actual run history after publishing.

  • Draft validated and expected trace reviewed.
  • Customer copy, forms and destinations checked.
  • Correct live version published.
  • Intended agent assignments saved.
  • Matching and non-matching real-channel tests completed.

Good to know

Publishing and assigning are separate controls. A published workflow without an assignment has no intended agent audience.

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

My latest changes are absent

Check whether they are an unpublished draft, and whether assignments were saved.

Was this article helpful?

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