Hi everyone,
I put together a new video overview of automation orchestrator, a visual workflow canvas add-on for Red Hat Ansible Automation Platform:
Automation orchestrator extends the Ansible automation you’ve already built into more complex, end-to-end IT operations workflows. It doesn’t replace your playbooks, job templates, roles, collections, or Event-Driven Ansible rulebooks. Instead, it lets you bring those existing automation assets onto a visual canvas as reusable workflow nodes—without rewriting them.
In the video, I walk through:
-
00:53 – Multiple ways to trigger a workflow: Bring manual, scheduled, webhook, and Event-Driven Ansible triggers together on one canvas.
-
01:55 – Reuse and portability: Use existing job templates, roles, and collections as workflow nodes, then export the complete workflow as a single YAML file for backup, sharing, Git-based version control, and configuration-as-code practices.
-
02:51 – More flexible workflow logic: Use branch, loop, converge, and switch nodes to route automation across multiple paths using real infrastructure data—not only binary success/failure results.
-
04:26 – Governed AI-assisted operations: Add task agents that analyze unstructured information, such as alerts or tickets, and recommend the next action. Approval gates, predefined policies, and audit trails remain in place before Ansible executes a change.
The visual canvas is the workflow authoring experience, but the workflows aren’t locked inside the UI. They can be exported as YAML, stored in Git, reused across teams, and imported into other environments. This also makes them useful for building more composable automation exposed through portals and other interfaces.
If you’re already using AAP and thinking about how to connect individual automation jobs into larger operational processes—or you’re evaluating where orchestration fits into your IT operations strategy—I’d love to hear what use cases you’re considering and what questions you have.
Learn more: Red Hat Ansible Automation Platform