System Triggers
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 consists of three components: a Trigger (when to run), a Launch Configuration (who can run it), and a Process (what it does). System triggers define the "when to run" condition, delivering events to your Process so the agent can reason and act.
Webhooks at a glance (Limited Preview)
- Create a Listener to capture events from providers (e.g., Salesforce, DocuSign, 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 (Limited Preview) and the Quickstart Guide.
Choosing the right trigger
- Select Webhooks for critical, real-time workflows.
- Choose Pollers for near-real-time reactions when source systems lack webhook support.
- Opt for Scheduled triggers for cadence-based tasks and periodic audits.
Execution flow (high level)
- Trigger Activates: An event, change, or schedule initiates the process.
- Moveworks Processes the Trigger: Validates and parses the trigger (e.g., a webhook).
- Matching Plugin(s) Execute: The configured Process runs, using LLM reasoning, API calls, and optional approvals.
- Logs Provide Traceability: Monitor each stage end-to-end during development and operations.
Updated 4 days ago