What’s new?
Workflow Maps now surfaces workflow execution errors across your sub-account in one place. Identify workflows that need attention, inspect their failed executions, and open the affected step to investigate.
Why this matters
A failed automation can interrupt lead follow-up, customer communication, or an internal handoff. Seeing errors across workflows helps your team find problems and understand what failed without checking each workflow separately.
How it works
Go to Automation > Workflows > Workflow Maps.
- Spot flagged workflows: An errors badge identifies workflows with errors from recent runs.
- Open the error summary: Select Review workflows with errors to see flagged workflows, grouped into Published and Draft.
- Focus your investigation: Use Has issues to narrow the map.
- Inspect the failure: Select a workflow and review its failed executions, affected step, and error details.
- Resolve the issue: Open the workflow in the builder to correct the affected step.
- Clear reviewed notifications: Return to the map and select Mark as read after reviewing the issue.
Common use cases
- Investigate failed webhook or integration actions.
- Review automation errors across a large sub-account.
- Identify failures affecting a customer’s follow-up sequence.
Additional notes
- Mark as read clears the error badge. It does not repair the workflow or retry a failed execution.
- Make the required workflow changes in the builder.
- Launch access: Workflow Maps is available only to agency users and agency admins at launch.
Preview
