Workflows · Flow Builder
Let business events move work through rules you can inspect.
Automation is hard to trust when nobody can see what triggered it, which rule ran or where it stopped.
This is a capability inside Lightning Pharos, not a separate product.
Choose an allowed event trigger and supported action.
01 · What ships
The complete working surface.
Selected business events routed into visible actions and failures.
- 01
A defined allowlist of business-event triggers
- 02
Recorded workflow runs with their current state
- 03
Email or pending-notification actions where delivery is configured
- 04
Task, activity, and ticket actions with failed, unavailable, and pending-human states kept visible
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Choose an allowed event trigger and supported action.
- 02 / 03
Governed event
A matching business event creates a recorded workflow run.
- 03 / 03
Connected result
Completed, failed, unavailable and pending-human states remain visible beside the run.
03 · What it needs
Ready inside every Pharos workspace.
This platform module is included with every workspace and is never sold as an add-on.
04 · Where it stops
The boundary is part of the product.
There are no arbitrary conditions, branches, record mutations, approvals, or money movement. Outbound webhook delivery is not implemented and reports unavailable.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system