The Problem
There is a significant gap when it comes to native event-driven notifications. Currently, if you want to receive a Teams or Slack message when a robot disconnects or a job faults, you cannot do this entirely within the UiPath ecosystem.
Here’s what you’d expect to be able to do natively:
- Robot disconnects → Send a Teams message
- Job faults → Send a Teams message with error details
- Queue processing completes → Send a summary notification
What You Actually Have to Do Today
To achieve this, you currently need to:
- Set up an Orchestrator Webhook to fire on events
- Route it to an external middleware tool (e.g. Power Automate, Azure Functions) to handle OAuth token exchange
- Use that middleware to either call back into UiPath via an API Trigger, or post directly to Teams yourself
This means relying on a Microsoft product (Power Automate) to glue together two things that are both already inside the UiPath platform. That’s a meaningful gap.
The Feature Request
I’d like to see UiPath introduce native event-driven notification actions directly within Orchestrator or Integration Service, for example:
- In Orchestrator Alerts: Extend the existing alerts system beyond email to support Teams, Slack, and webhook targets natively
- In Integration Service: Expose Orchestrator internal events (robot status, job state changes, queue events) as first-class triggers that can drive Integration Service workflows
- In Automation Ops / Monitoring: A built-in notification rules engine — “when X event happens, send message to Y channel”
Why This Matters
Operational visibility is critical for teams running automations at scale. Right now, the path of least resistance is to route everything through Power Automate, which adds external dependencies and maintenance overhead for what should be a straightforward platform capability.
This would be a high-value, high-visibility feature for operations teams and would strengthen UiPath’s case as a truly self-contained automation platform.
