Skip to content
Go to Dashboard

Workflows in Platform Connections

Overview

Every other Platform Connections page describes a template’s relationship to Workflows. Opened from a Workflow, the page turns around: it lists what this Workflow creates and what leads into it. That makes it the closest thing to a map of a Workflow’s reach across the rest of your Persona configuration.

Direct connections lists what the Workflow creates itself

Workflows and Inquiry Templates are the only two surfaces with a Direct connections section on the Creates tab. For a Workflow it lists the templates the Workflow can create directly.

A Workflow creates from a template through an action step that names one, so the entries here correspond to steps in the Workflow such as:

The Workflows section then shows whether this Workflow triggers any Workflows, which is one of the ways a Workflow run starts, and Downstream connections shows what those Workflows create in turn.

What leads into the Workflow

The Created By tab lists the upstream templates and Workflows that lead to the one you are viewing. A Workflow can also be started by an API call, a recurring schedule, or a person running it manually, and none of those starts comes from a template, so Created By is most informative for a Workflow triggered by an event on a template. Workflows overview lists the ways a run can start.

Check it before you publish

Connections is available for the latest published version, so it describes the Workflow as it currently runs rather than the draft you are editing.

That gap is worth respecting on Workflows in particular. An organization-level Workflow has one version history across environments, and publishing a new version publishes it everywhere at once, even though its state can differ per environment. Reading the Creates tab first tells you which templates a change will reach. See Organization-level Workflows and Workflow Versions and Change Management.

Was this article helpful?
Thanks for the feedback. It helps us improve these docs.