> This page is for Tools.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.moveworks.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server.

# System Triggers

System triggers power proactive automation in [Ambient AI agents](/ai-assistant/ambient-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

| Trigger                                                          | Summary                                                                         | Responsiveness | Typical objective                | Example                                                             |
| ---------------------------------------------------------------- | ------------------------------------------------------------------------------- | -------------- | -------------------------------- | ------------------------------------------------------------------- |
| **[Webhooks](/tool-studio/system-triggers/webhook-triggers)**    | 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 |
| **[Scheduled](/tool-studio/system-triggers/scheduled-triggers)** | Run at predefined times or intervals                                            | Periodic       | Keep time-based workflows moving | Every Monday 9am → review feature requests and route to PM          |

\


## How triggers connect to your processes

In Tool 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](/tool-studio/system-triggers/webhook-triggers) and the [Quickstart Guide](/tool-studio/system-triggers/webhook-triggers#quickstart).

## 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

```mermaid
flowchart TD
    A[Event/Schedule Occurs] --> B[Trigger Activates]
    B --> C[Moveworks Validates & Parses]
    C --> D[Route to Matching Plugin]
    D --> E[Process Executes<br />LLM + APIs + Approvals]
    E --> F[Log Results for Traceability]
    style A fill:#e1f5fe
    style F fill:#f3e5f5
```

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.

## In This Section

* [Webhooks Triggers](/tool-studio/system-triggers/webhook-triggers)
* [Scheduled Triggers](/tool-studio/system-triggers/scheduled-triggers)
* [Cron Expression Examples](/tool-studio/system-triggers/scheduled-triggers/cron-expression-examples)
* [System Triggers Logs & Troubleshooting Guide](/tool-studio/system-triggers/webhook-logs-troubleshooting-guide)