Skip to navigation
Agent StudioCookbooks

Ambient Agents Cookbook

View as Markdown

Ambient agents can leverage different trigger types, each with its own architecture for handling events, changes, or scheduled tasks. Below are sequence diagrams illustrating the flow for each trigger type.

Webhook Trigger Architecture

This diagram shows an ambient agent responding to a real-time webhook event, such as monitoring CPU usage and scaling resources if needed.

alt [CPU Usage > 80%] [CPU Usage ≤ 80%] Monitor Webhook Trigger Send Webhook Event (CPU Usage) Interpret and Validate Event Check: Is CPU Usage > 80%? Execute Action (Scale Resources) Return Result Log Event Deliver Notification Admin Ambient Agent Backend System 1

Scheduled Trigger Architecture

This diagram depicts an ambient agent executing a workflow at a predefined time, such as generating a report on new feature requests every Monday morning.

Do not use scheduled triggers to run a task for every employee. Instead, you should aim to run a task for every record in a business process.

Scheduled Trigger (Every Monday @ 9am) Get All New Feature Requests Return Feature Request Data Compare to WIP Memos Identify Relevant PM Assign Task to PM Return Assignment Result Generate Summary Report Deliver Report Receive Report Admin Ambient Agent Backend System 1 Backend System 2

.