> ## Documentation Index
> Fetch the complete documentation index at: https://docs.workflowmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Triggers

> Learn what triggers are, what kinds of triggers Workflow Machine supports, and how to choose the right one.

## What a trigger is

A trigger is what starts a workflow.

Without a trigger, a workflow has nothing to react to. The trigger defines the real-world event or schedule that causes the automation to begin.

## Common trigger types

Workflow Machine supports several useful trigger patterns.

### Webhook triggers

Webhook triggers start a workflow when another system sends data into Workflow Machine.

Use a webhook when:

* another tool can send HTTP requests
* you want to start the workflow from a custom system
* you need direct control over the input payload

Webhook triggers are flexible and often a strong first choice for integrations that do not have a native trigger.

### Schedule triggers

Schedule triggers run a workflow at a time or interval you define.

Use a schedule when:

* the workflow should run repeatedly
* the workflow is based on time rather than an external event
* you want a recurring digest, sync, or cleanup process

Examples include daily summaries, periodic checks, and timed reminders.

### RSS triggers

RSS triggers monitor feed updates and start a workflow when new content appears.

Use an RSS trigger when:

* you want to monitor blogs, news sources, or other feed-based content
* you want to collect or summarize updates on a recurring basis

### App event triggers

Some connected apps provide native events that can start workflows.

Use an app trigger when:

* the integration already exposes the event you need
* you want less custom setup than a webhook
* you want the workflow to start closer to the source app itself

## How to choose the right trigger

Pick the trigger that matches the natural starting point of the process.

A simple decision guide:

* choose **Webhook** when another system sends data to you
* choose **Schedule** when time is the main driver
* choose **RSS** when feed updates are the source
* choose an **App event** when the integration already supports it

If you choose the wrong trigger model, the workflow can become harder to maintain than it needs to be.

## What makes a good trigger

A good trigger is:

* easy to explain
* easy to test
* closely tied to the real event you care about

For example, “new form response” is a better trigger idea than “run every minute and check whether a form changed,” unless a schedule is the only option available.

## Trigger design tips

When planning a workflow, ask:

* what exact event should start this process
* how often should it happen
* what data will the trigger provide
* is this input stable enough for downstream steps

Those questions usually surface the right trigger choice quickly.