> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.moveworks.com/agent-studio/core-concepts/ambient-agents/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server.
# Ambient Agents
Ambient agents monitor enterprise systems continuously, detecting events or changes to initiate workflows automatically.
> **Info**
>
> In Agent Studio, you create an ambient agent by setting a plugin's **Trigger Type** to **System** (either Webhook or Schedule). The term "ambient agent" describes the pattern — the UI uses "System trigger" for the configuration.
# Ambient Agent Architecture
Ambient agents follow the **Listen → Understand → Act** cycle.
```mermaid
flowchart LR
A[Listen
Detect signals
via triggers] --> B[Understand
Interpret with LLMs & context]
B --> C[Act
Execute via APIs, scripts, & approvals]
style A fill:#e1f5fe
style B fill:#f0f4c3
style C fill:#ffebee
```
## Listen
Monitor systems for events, data changes, or schedules using [System Triggers](/agent-studio/system-triggers). Examples include new tickets, inactive licenses, or supply chain alerts.
## Understand and Act
Events are fed into a [Compound Action](/agent-studio/actions/compound-actions#/) in both phases:
* **Understand**: Analyze the event with an LLM to interpret context and assess impact.
* **Act**: Execute [Actions](/agent-studio/actions/compound-actions/action), including API calls, scripts, or approvals.
### Sending Notifications
To send messages or interactive notifications with action buttons to users, use the [`notify` compound action expression](/agent-studio/actions/compound-actions/notify). The `notify` expression supports:
* Rich text messages with dynamic data via `RENDER()`
* **Action buttons** with three types: `content_action` (inline message), `system_action` (triggers an action), and `conversation_action` (starts a conversational process)
* Targeting specific users via `recipient_id`
See [Quickstart #5: Notification Ambient Agent](/agent-studio/quickstart-guide/webhook-triggers-quickstart-guide) and [Quickstart #7: Scheduled Trigger Ambient Agent](/agent-studio/quickstart-guide/quickstart-7-scheduled-trigger-ambient-agent) for complete examples.
# How Ambient Agents Work
System triggers handle the **Listen** phase and feed events into a Compound Action to **Understand** and **Act**. They use LLMs for reasoning, APIs for integration, and logs for observability.

\
# Example Use Cases
Ambient agents enable powerful automations across various business functions.
Here are some real-world examples:
* **SaaS License Reclamation**: An ambient IT agent that scans weekly for inactive SaaS licenses, confirms inactivity with the user, reclaims the unused licenses, and saves real dollars every week.
* **Support Ticket Auto-Triage**: An ambient customer support agent that triages new high-priority Jira tickets, attempts to reproduce issues using internal tools, looks for related open tickets, and summarizes its findings, all before a human support agent even opens the ticket.
* **Supply-Chain Disruption Response**: An ambient supply chain agent that detects potential disruptions, diagnoses the root cause, and then recommends and executes adjustments once approved.
You can brush up on best practices for [Ambient AI agents in our cookbooks](/agent-studio/cookbooks/ambient-agents-cookbook#/).
# Get started
1. Review the **[System Triggers Overview](/agent-studio/system-triggers#/)**
2. Build with **Webhook Triggers** via the [Quickstart](/agent-studio/system-triggers/webhook-triggers#/)
3. Debug and iterate using [Logs & Troubleshooting](/agent-studio/system-triggers/webhook-logs-troubleshooting-guide#/).
## Docs
- [Connecting Ambient Agents to Conversational Agents](https://docs.moveworks.com/agent-studio/core-concepts/ambient-agents/connecting-ambient-agents-to-conversational-agents.md)
- [Ambient Agent FAQs ](https://docs.moveworks.com/agent-studio/core-concepts/ambient-agents/ambient-agent-faqs.md)