> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/automations/triggers.md).

# Triggers

Learn about how triggers and scheduling work with Couchdrop automations

## Overview

Workflow triggers define how a Couchdrop workflow starts. Choose the trigger type based on whether the workflow should run on a schedule, react to an event, be started by a user or external system, or only run manually.

### Scheduled Triggers

Scheduled Triggers run a workflow on a defined schedule.

Use a Scheduled Trigger for repeatable workflows, particularly when Couchdrop needs to connect to a remote system and perform an action at regular intervals.

For example, you might schedule a workflow to periodically check a remote server for files and transfer them into another location.

### Event Triggers

Event Triggers start a workflow when a specific event occurs.

They are useful when files arrive at unpredictable times or when a workflow should react to file activity rather than run on a fixed schedule.

### Runnable Actions

Runnable Actions allow users to run a workflow without giving them access to edit the workflow itself.

This is useful when you want to make a predefined process available to other users while keeping the workflow configuration controlled.

### External Webhook

An External Webhook provides a webhook URL that an external system can call to start the workflow.

Use this trigger when another application or service needs to initiate a Couchdrop workflow as part of a wider process.

### Manual Activation

Manual Activation workflows only run when they are started manually from the workflow builder.

This is useful for testing workflows or for processes that should only run when explicitly initiated by an administrator.