System Triggers Overview

System triggers are the foundation of ambient agents. They initiate workflows based on events, changes, or schedules so work moves forward automatically.

Trigger types

Trigger	Summary	Responsiveness	Typical objective	Example
Webhooks	Event-driven; fire in real time when a specific event occurs in a source system	Instantaneous	Respond to key business events	“Gong call completed” → extract key details and propose CRM updates
Pollers	Pull-based; periodically check systems that don’t support webhooks	Near-instantaneous	Detect important changes	Account health drops from Green → generate get-well plan
Scheduled	Run at predefined times or intervals	Periodic	Keep time-based workflows moving	Every Monday 9am → review feature requests and route to PM

📘
Availability
Webhooks are in Limited Preview; Scheduled and Pollers are coming soon.

How triggers connect to your processes

In Agent Studio, a Plugin is made of three parts: a Trigger (when to run), a Launch Configuration (who can run it), and a Process (what it does). System triggers populate the “when to run” side — handing events into your Process so the agent can reason and act.

Webhooks at a glance (LP)

You create a Listener to receive events from providers (e.g., Salesforce, DocuSign, Asana).
Moveworks validates incoming events (supports signed secrets and one-time challenge verification).
Events are parsed and dispatched to matching plugins. Observability is available via dedicated logs.

For hands-on steps, see Webhook Triggers (Limited Preview) and the Quickstart Guide.

Choosing the right trigger

Pick Webhooks for critical, real-time workflows.
Use Pollers when the source system can’t emit webhooks but you still need near-real-time reactions.
Use Scheduled for cadence-based jobs and periodic audits.

Execution flow (high level)

Trigger fires (event, change, or schedule).
Moveworks processes the trigger (e.g., validates & parses a webhook).
Matching plugin(s) run the configured Process—LLM reasoning, API calls, and optional approvals.
Logs help you trace each stage end-to-end during development and ops.