Build a workflow in the portal

A workflow is a trigger, followed by optional conditions, followed by actions — you build the whole chain visually, no code required. This article walks through building one in the portal. For the concepts behind it, see what workflows are.

Open Workflows

In the portal sidebar, go to Orchestrate → Workflows. If you don't see it, availability can vary by org — reach out to Nash if you'd like access.

Create a workflow

Select New Workflow and give it a name. You'll land in the workflow editor, where you build the trigger, conditions, and actions.

Choose a trigger

Every workflow starts with a trigger — the order, delivery, or job event that kicks it off. Pick one from the trigger list to start building. See triggers, conditions, and actions for the full list of what's available.

Add conditions (optional)

Conditions narrow when a workflow runs — for example, only continue if the order value is over a threshold. Combine multiple conditions with AND/OR to match exactly the situations you care about. See triggers, conditions, and actions for the operators available.

Branch (optional)

Add a branch to send jobs down different paths from the same workflow, rather than building separate workflows for each case.

Add actions

Actions are what Nash actually does once a trigger fires and its conditions pass — for example, set a dispatch strategy or send a Slack message. See triggers, conditions, and actions for the full catalog of actions.

Save, test, and activate

Select Save Workflow to save your changes. Before relying on a workflow, use Test or Run to try it out. Once you're confident it works, see run a workflow manually to try it against existing orders, and monitor its runs to keep an eye on it once it's live.

Manage your workflows

From the Workflows list, you can duplicate a workflow to reuse as a starting point, or archive one you're no longer using. Export a workflow to JSON and import it into another workflow to reuse its configuration elsewhere. Workflows also carry Draft and Template statuses, alongside active ones, so you can tell what's ready to run from what's still in progress.