--- title: Triggers slug: triggers docTags: createdAt: 2025-08-11T11:13:48.000Z --- A **trigger** starts a playbook run. A playbook can define more than one trigger; each **flow** uses one trigger at a time. Add most triggers from the **Playbook Canvas Add** panel, then drag the trigger onto the canvas. Turbine has the following trigger types: | **Trigger type** | **Typical use** | | ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Using Webhook Triggers in Swimlane Turbine](https://docs.swimlane.com/using-webhook-triggers-in-swimlane-turbine) | External systems POST or GET to a Turbine URL to start or supply payload data. | | [Record Event Triggers](https://docs.swimlane.com/record-event-triggers) | Create, update, or delete on selected applications or records. | | [Schedule Triggers](https://docs.swimlane.com/schedule-triggers) | Time-based or cron-style runs. | | [Playbook Button Triggers](https://docs.swimlane.com/playbook-button-triggers) | Users start a run from the Canvas or from an application. | | [Flow Event Trigger](https://docs.swimlane.com/flow-event-trigger) | Another flow or playbook activity drives execution (orchestration between flows). | | [DateTime field trigger](./#datetime-field-trigger) | Runs a flow when a record **Date/Time** field value (± offset) is reached. Added from Application Builder field settings, not from the canvas Add panel. | :::hint{type="info"} The [Playbook Button Triggers](https://docs.swimlane.com/playbook-button-triggers) type is also available via applications. ::: ::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/eWKDpgleDCPpLMADMPHV4_canvas-addpanel-triggers.png" size="38" width="345" height="356" darkWidth="800" darkHeight="826" position="center" showCaption="false"} Continue to the following sections for details and configuration of each type of trigger. For DateTime field triggers, start in Application Builder — see [Select Fields and Assign Field Properties](Select%20Fields%20and%20Assign%20Field%20Properties.md)#datetime-field-triggers. ## DateTime Field Trigger Starting in **Turbine 26.3.0**, a **DateTime field trigger** starts a playbook flow when a record's **Date/Time** field reaches the configured fire time (field value plus optional offset). ### How You Add It - Configure **Trigger Playbook** on a **Date/Time** field in Application Builder (**Advanced** → **Configure**). - Saving the application adds the DateTime field trigger to the selected flow automatically. - The DateTime field trigger is **not** listed in the canvas **Add** panel. You cannot create one by dragging a trigger onto the canvas. ### How It Appears on the Canvas When a flow has a DateTime field trigger, the trigger details panel shows read-only values: | **Field** | **Description** | | ------------------- | ------------------------------------------------------- | | **Application** | Application that owns the Date/Time field. | | **Date/Time Field** | Field that drives the schedule. | | **Offset** | Configured offset and unit relative to the field value. | Notice tip in the UI: **Configured via the Application's field settings.** Playbook run history currently labels these runs as **Delay Trigger** (canvas label is **DateTime field trigger**). ### Record Data Passed to the Playbook When a DateTime field trigger fires, the playbook receives the **full record** for that application—field schema and values—not only the tracking ID. Downstream actions can map record fields from the DateTime field trigger output the same way they do for a **record event** trigger. You do not need a separate lookup that starts from tracking ID alone to read other field values. The tracking ID remains available as part of the record data. ### Scheduling Behavior - **Record create** with a Date/Time value schedules a run. - **Record update** that changes the Date/Time value reschedules the pending run. - **Clearing** the Date/Time value or **deleting** the record cancels the pending run. - Deleting the field, clearing the field configuration, or deleting the linked playbook or flow removes or clears the DateTime field trigger and cancels outstanding schedules. Solution Builder warns when delete or disable actions would clear DateTime field trigger configuration from linked applications. ### Flow Sharing Rules Starting in **Turbine 26.3.3**, Application Builder save validation uses these rules: | **Assignment** | **Can share one flow?** | | ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | | Two or more playbook buttons | Yes | | A playbook button and correlation | Yes | | A DateTime field trigger and a playbook button, correlation, or another DateTime field trigger | No. Assign the DateTime field trigger to a flow that no other trigger uses. | If you save an application and see **Duplicate flow assignments across triggers**, the DateTime field trigger is sharing a flow. Point the DateTime field trigger at an unused flow, then save again. ### Limits and Scope (Phase 1) - Offset units: **Minutes** or **Hours**. - Maximum absolute offset: **7 days**. - Phase 1 covers time-based field triggering only. Dedicated SLA field types are planned for later releases. ### See Also - [Select Fields and Assign Field Properties](Select%20Fields%20and%20Assign%20Field%20Properties.md)#datetime-field-triggers — configure offset, playbook, and flow - [Configuring Playbooks](Configuring%20Playbooks.md) — playbook configuration overview - [Application Builder](Application%20Builder.md) — save validation for shared flows - [Schedule Triggers](https://docs.swimlane.com/schedule-triggers) — recurring or cron schedules (different from DateTime field trigger)