Skip to content
Workflows

Import, export and migrate workflow configurations

Reuse a reviewed configuration while checking its local dependencies.

Where to find itWorkflows → import/export / legacy import

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

    Export before a large change

    Save the supported export format outside the editor. Exports can contain copy and configuration; treat them as internal business data.

  2. 2

    Import into a draft

    Use the supported import action and inspect validation results. Do not assume agent IDs or destinations from another workspace remain valid.

  3. 3

    Review migrated legacy rules

    Older per-agent outreach/contact settings are moved into central workflows through the migration controls. Review each imported rule; some lead rules begin as drafts.

  4. 4

    Retest local dependencies

    Check agent assignments, pages, contact fields, handoff destinations and provider approvals. Publish only after a real test.

Good to know

The workflow format is validated. Arbitrary code, background cron jobs and unsupported HTTP actions do not become supported through an import file.

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

Old and new invitations both appear

Check whether the legacy rule was fully migrated and whether another published workflow duplicates it.

Was this article helpful?

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