Port Workflows vs Actions and Automations
On this page
Quick answer
Choose Workflows for multi-step graph orchestration with conditions, approvals, agents, shared permissions, and audit across entry points. Keep an existing Action or automation when it remains a small, stable operation and migration would add no user or control value.
Do not migrate by name alone. Inventory current triggers, forms, permissions, identities, integrations, secrets, retries, logs, approvals, outputs, and consumers.
Migration decision
| Need | Better starting point |
|---|---|
| One bounded self-service operation | Existing Action may be sufficient |
| Event-driven single automation | Existing automation may remain simpler |
| Multi-step conditions and branches | Workflow |
| Human approval inside the graph | Workflow |
| Agent or MCP entry with shared controls | Workflow |
| Common audit and output contract across entry points | Workflow |
Run both paths against representative cases, compare authorization and outputs, then cut over one cohort. Preserve a rollback window and avoid duplicate triggers during migration.
Continue with the GA guide and IaC authoring guide.
Official sources
Source check: August 23, 2026. Verify current legacy and Workflows behavior in the target account.