Workflow builder or tenant administrator

Build the first workflow as a small, visible business path

A workflow is a versioned definition of how an event becomes an outcome. The safest first workflow is short enough to explain on one screen. For Northstar, the trigger is lead.created, the condition checks service and budget, the guarded step requests approval, and the observable action creates a discovery task.

Outcome: You will create an inactive workflow draft for the Northstar lead story.
For: Workflow builder or tenant administrator
Time: 30 minutes

Before you start

A tenant user with workflow permissions.
A fictional test payload.
A clear trigger and visible outcome.

Build the first workflow as a small, visible business path diagram — Build the first workflow as a small, visible business path — a text description is included inside the diagram and in the surrounding section.

#Understand the node types

Trigger

The event that starts a run: record event, schedule, lead event, connector event, or signed webhook.

Condition

A rule that selects a path using explicit facts.

Action

A bounded change such as creating work, notifying someone, or calling a typed connector operation.

Wait

A durable pause until a time or supported state.

Approval

A human decision before a guarded action continues.

Subworkflow or batch

Reuse a proven process or handle a bounded collection predictably.

#Create the Northstar draft

Open Workflows and create an inactive draft named “Qualify consultation lead.”
Add the lead.created trigger and document the expected fields.
Add a condition for Automation plus a budget of at least 5,000.
Add a manager approval to the qualified branch.
Add task creation and owner notification after approval.
Add a safe fallback that records an ordinary follow-up instead of discarding the lead.

#Use the builder deliberately

The node library adds capabilities; the canvas explains order and branches. Save regularly, keep labels business-readable, and inspect the definition preview before validation. A visually connected node is not automatically valid: required configuration, mappings, permissions, and provider readiness still apply.

FlowOS workflow list with draft and run controls — Keep the first workflow inactive while building. Capture details

FlowOS visual workflow builder — The canvas makes trigger-to-outcome order visible. Capture details

FlowOS workflow node library — Choose the smallest set of nodes that explains the process. Capture details

#Common mistakes

Branching on facts that do not change an action.
Putting secrets into node labels or ordinary variables.
Using an external write as the only proof that a test ran.

#Verify the result

The trigger and expected payload are documented.
Every branch has an intentional outcome.
The workflow remains inactive.
Guarded effects require approval.