All About Automation Cloud Services

  Catch the recording at

.

Previously, on Dev Meetups…

If you caught April's session where we built a power workflow with Split & Merge and Universal Web Triggers, May was the natural follow-up: a closer look at the roster of updates to Automation Cloud Services - with a special emphasis on what event-driven automation actually looks like in practice.

​@Vineet Pujari  (Principal Product Manager, Automation Cloud Services) walked us through the full web triggers catalogue, and ​@Shreya.Kumar demoed a GitHub issue assignment workflow live.

Universal Web Triggers are...Universal [03:28]

if you've ever signed up for a Pathfinder event and gotten a confirmation email straight to your inbox, you’ve seen Web Triggers in Action. The moment you register for an event, an API task fires and the email lands into your inbox.

Web triggers listen for an event, and when it happens, they hand the context off to an automation. No bot runner sitting idle. No polling on a schedule. Just event triggered automation.
 

🔴 The Live Demo: Web Triggers → Mozart Orchestrator [09:00]

The demo Vineet ran was a large order workflow. Most enterprise teams know this scenario well: a high-value order comes in, goes on hold, and then sits in a queue waiting for someone to review it. He demo’ed how to wire up a Universal Web Trigger so that the moment an order goes on hold in the source system, the event payload lands in a Mozart Orchestrator process automatically — no manual kick-off required.

The setup is done in 3 easy steps:

1. Create a listener (Manage → Event Triggers → Listeners),
2. Add the Universal Web Trigger to your process and select that listener.
3. Register the process under Manage Event Triggers to activate it.

After that, the control room is listening. Anybody who sends a payload to that URL starts the process.

Watch Vineet demo this workflow.

🤖 Hands-on Demo [47:36]

Shreya's demo touched upon a problem that a lot of open source maintainers will be familiar with. Open source projects at a massive scale like PyTorch have thousands of open issues and a constant influx of new contributors everyday. Getting the right issue in front of the right contributor can mean the difference between a successful first contribution and a contributor who never comes back. The challenge is deciding and assigning the right contributor to the right issue.

In the demo, this problem was illustrated using a GitHub repository with 15 open issues and a small pool of contributors. While the example was intentionally small, it mirrors the same decision-making challenge that large projects face with 5,000+ open issues and hundreds of potential contributors. The question becomes: how do you make those assignments quickly, fairly, and effectively?

First, we demoed a Python script scored issues by label weight (bug = 3, help wanted = 2, good first issue = 1) and assigned based on experience tier. Clean, fast, explainable — and it ran on Automation Cloud Services without any Python installation or bot runner required.

Then that API Task, along with the rest of the tools — GetIssues, GetCommentHistory, SummarizeAndRecommend, etc — were handed to the AI Agent.

The Goal Based AI Agent was in charge of the overall orchestration. It ran the issue fetches in parallel on its own (it eevn figured out that getting comments for issues are not interdependent), and made recommendations from unstructured contributor data.

Even without giving a predetermined path, the goal based agent was able to successfully reason which tool to call, which tools depended on others for input and which ones could be called in parallel.

💡Pro Tip: To make your agentic workflow auditable, add a reasoning output variable to your agent to return the rationale alongside the decision.

Up Next...

The next dev meetup is on August 27th. This is a special one, because winners of our Pathfinder Hackathon will showcase their demos at this meetup. Sign up here to watch them: https://community.automationanywhere.com/events/pathfinder-hackathon-winner-showcase-467

If you’d like to present a use case, or have a half-formed idea for one, reach out to us at 📧 community@automationanywhere.com to present it at the next Dev Meetup.