Skip to main content

Build and test workflow automations

Create a pipeline-triggered workflow, configure its graph, test it safely, and publish deliberately.

Written by Geoff Mina

Workflow automations connect sales-pipeline events to repeatable communication, client, billing, project, and portal actions.

Open Workflow automations

Create the workflow and trigger

Select New workflow, give it a recognizable name, and choose the pipeline stage that starts it. The trigger cannot be changed after creation, so confirm the stage before building the flow.

Moxie Workflow automations list with search, filters, and create actions

The workflow library is where you find drafts, active automations, and execution activity.

Build on the canvas

Add or drag steps from the library onto the grid. Workflows can wait, make Yes/No decisions, send messages and documents, create clients or projects, move an opportunity, send an invoice, or request a form. Multiple branches may converge into the same downstream step.

Moxie workflow builder showing the workflow name and save state, the Active or Disabled switch, Undo, Redo, Activity, Test, Save, and Publish controls above the step library and canvas

The example is disabled, so it can be configured and tested without running automatically.

Edit, test, save, and publish

The builder header keeps the workflow's controls together. Rename the workflow directly in the name field; the label beneath it shows Unsaved changes, Draft saved, or Published. The Active/Disabled switch controls whether the workflow runs automatically, and Undo, Redo, and Activity sit beside Test, Save, and Publish.

  • Single-click a node to select or move it; double-click it, or press Enter while selected, to open its settings.

  • Select a connection to delete the connection without deleting either node.

  • Use Test to run the current graph in the browser with mock data. The emulator does not send messages, create records, or execute backend actions.

  • Save stores the draft. Publish validates the flow and makes that draft the live workflow.

  • Keep the workflow disabled until its branches, templates, senders, and test results are correct.

Important: Email, phone, template, and payment-dependent steps require those underlying workspace settings to be complete.

Extend workflows beyond Moxie

Workflow automations run Moxie's native business processes. When an external application needs Moxie data or event notifications, use the separate Custom API and event webhooks guide.

Continue exploring Settings & administration

Previous
​← Create and organize reusable templates

Next
​Configure project, pipeline, and custom-field rules →

Back to Settings & administration

Did this answer your question?