Build your first workflow

Workflows run when records change — for example when a lead hits a stage or an invoice is overdue.

Please note:

• Test workflows in Draft before activating — unintended loops can spam users via Notifications overview.
• Approval steps pause automation until someone acts — see Workflow approvals for routing and timeouts.
• Workflow actors need module access and the right permissions — confirm roles in Roles, permissions, and RBAC and enable the target module under Enable and manage modules.

Workflow parts

Part	Examples	Notes
Trigger	Record created, field changed, schedule	One trigger per workflow
Condition	Stage equals, amount above threshold	Narrow to avoid loops
Action	Notify, update field, assign, approval	Chain multiple actions
Status	Draft, active, paused	Test in draft first

Create a workflow

1. Open Workflows
2. Choose a trigger (record created, field changed, schedule)
3. Add conditions and actions (notify, update field, assign)
4. Activate when ready

Guardrails

• Start with a narrow condition set
• Test on a sample record before enabling for everyone
• Document who owns each automation

flowchart TB
  Trigger[Trigger fires] --> Conditions{Conditions met?}
  Conditions -->|No| Stop[No action]
  Conditions -->|Yes| Actions[Run actions]
  Actions --> Notify[Send notification]
  Actions --> Update[Update field or assign]
  Actions --> Approval[Approval step optional]
  Approval --> Done[Workflow complete]

Workflows respect the same module and permission model as the rest of EDGE Sword.