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
      • Webhooks Triggers
      • Scheduled Triggers
      • System Triggers Logs & Troubleshooting Guide
    • Agent Architect
    • Cookbooks
    • 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
  • Trigger types
  • How triggers connect to your processes
  • Webhooks at a glance
  • Choosing the right trigger
  • High Level Execution flow
Agent Studio

System Triggers

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

Webhooks Triggers

Next
Built with

System triggers power proactive automation in Ambient AI agents, enabling workflows to launch automatically in response to real-time events, data changes, or scheduled intervals. This shifts your agents from reactive tools to intelligent, always-on systems that anticipate and resolve issues before they escalate.

Trigger types

TriggerSummaryResponsivenessTypical objectiveExample
WebhooksEvent-driven; fire in real time when a specific event occurs in a source systemInstantaneousRespond to key business events“Gong call completed” → extract key details and propose CRM updates
ScheduledRun at predefined times or intervalsPeriodicKeep time-based workflows movingEvery Monday 9am → review feature requests and route to PM

How triggers connect to your processes

In Agent Studio, Plugins are modular workflows built around two essential elements:

  • Trigger: Defines the activation condition (when to run)
  • Process: Outlines the sequence of actions (what it does)

System Triggers feed events directly into the Process, enabling end-to-end automation without manual intervention, allowing the agent to reason and act.

Webhooks at a glance

To configure webhooks:

  • Create a Listener for event providers like Salesforce or Asana.
  • Moveworks validates incoming events, supporting signed secrets and one-time challenge verification.
  • Events are parsed and dispatched to matching plugins, with observability provided through dedicated logs.

For hands-on steps, see Webhook Triggers and the Quickstart Guide.

Choosing the right trigger

  • Use Webhooks for real-time responses to system events.
  • Use Scheduled for recurring tasks like weekly audits.

High Level Execution flow

  1. Trigger Activates: An event, change, or schedule initiates the process.
  2. Moveworks Processes the Trigger: Validates and parses the trigger (e.g., a webhook).
  3. Matching Plugin(s) Execute: The configured Process runs, using LLM reasoning, API calls, and optional approvals.
  4. Logs Provide Traceability: Monitor each stage end-to-end during development and operations.