For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
ReferenceGuides
ReferenceGuides
  • Agent Studio
    • Overview
    • Quickstart Guides
    • Core Concepts
    • Conversation Process
    • Actions
    • Connectors
    • System Triggers
    • Agent Architect
    • Cookbooks
      • Data Retrieval Cookbook
      • Ambient Agents Cookbook
      • Connect to other AI Agents & Applications
      • Mirroring Approvals
      • Plugin Architecture Guide
      • Agent Studio Design Philosophy
      • Integrating External Webhooks
      • Data Transaction Cookbook
      • When to Use Compound Actions vs. Conversational Processes
    • Development and Testing
    • AI Agent Marketplace
    • Developer Tools
  • Agentic AI
    • LLM Fundamentals
    • The Agentic Reasoning Engine
    • Memory Constructs
    • Conversational Context
    • Guardrails
    • Grounding and Hallucinations
    • Continuous Learning
    • LLMs & SLMs
    • Steerability Tools
    • Multilingual Support
  • Core Platform
    • User Identity
    • Moveworks Agent (On-Prem)
    • Approvals Engine
    • Entity Catalog
    • Moveworks Data Objects
    • Security Information and Event Management (SIEM) Logs Overview
DeveloperAcademyCommunityStatus
On this page
  • Webhook Trigger Architecture
  • Scheduled Trigger Architecture
Agent StudioCookbooks

Ambient Agents Cookbook

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Connect to other AI Agents & Applications

Next
Built with

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.

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.

.