> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/triggers-and-scheduled-and-event-runs.md). # Triggers and scheduled and event runs Triggers start a workflow when a schedule or supported external event occurs. Use them for work that should begin without a person submitting each request. {% embed url="" %} ## Before you start Have a working workflow and permission to publish its configuration. This guide walks through a schedule; for provider events, see **Use an external event** below. A draft schedule does not run automatically. Complete publication and check registration before waiting for the first scheduled run. ## Connect the trigger Connect Scheduled Execution to the processing steps and Output. ![Scheduled Execution connected to processing steps](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/hxcX1OLHH5CPoDCfn9qf/assets/g031-g031-01-version-preview.png) The schedule starts this path automatically when its registration is enabled. ## Set the schedule Open Scheduled Execution → Configuration and set the frequency, time, and time zone. ![Schedule frequency, time, and time zone](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/AMvzOhQaNrTS1AIhhRQC/assets/g031-g031-02-schedule-config.png) Check the time zone carefully so the schedule runs at the intended local time. ## Use the trigger data Insert the Scheduled Execution reference into the step that consumes its payload. ![Scheduled Execution payload reference](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/sSgz99NsvjvpYfzGXyeV/assets/g031-g031-03-payload-mapping.png) A live reference passes the trigger's actual value into the workflow. ## Publish the schedule Save the draft and [publish the configuration](/guides-and-quickstarts/releases-and-environments/publish-and-unpublish-a-project.md). If your organization requires approval, follow [Deployments and approval requirements](/guides-and-quickstarts/releases-and-environments/deployments-and-approval-requirements.md). Check the schedule’s time zone and choose a future occurrence that you can observe. ## Check trigger registration Open Settings → Integrations → Triggers and review the registration status. ![Trigger registration status in Settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/RsqmjVb1q5k2KIkJrVRm/assets/g031-g031-05-trigger-disabled.png) A schedule configured inside a workflow must also have an enabled registration to run automatically. ## Inspect scheduled runs Open Analytics and inspect a run whose type is Scheduled. ![Scheduled run details in Analytics](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/g9U9di7ZwGTIA6OhRlnj/assets/g031-g031-04-scheduled-run.png) Check its status, time, input, and output to confirm what happened during that occurrence. ## Important behavior Save and deploy the required configuration. Schedule fields in an unpublished draft do not activate a schedule. If no scheduled run appears, check the registration status, deployed version, schedule, and time zone. ## Use an external event For event-driven work, choose the trigger provided by the application that produces the event, supply its required connection and configuration, and connect it to the processing path. The event fields vary by provider, so inspect that trigger’s available outputs when mapping downstream inputs. Use [Provider connector configuration](/guides-and-quickstarts/using-tools-and-actions/provider-connector-configuration.md) for connection setup and [Manage configured triggers](/guides-and-quickstarts/using-tools-and-actions/manage-configured-triggers.md) to locate and review the registration. Publish the required configuration and check that its registration is enabled. Then cause an event that matches the trigger’s configured conditions and inspect the resulting execution in Analytics. A manual run tests the processing path; it does not prove that the external event listener is active. --- # 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.stackai.com/guides-and-quickstarts/workflow-builder/triggers-and-scheduled-and-event-runs.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.