> 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.couchdrop.io/automations/triggers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.