Triggers

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 docid\ be3ikvbsy hvvndx3 ruu external systems post or get to a turbine url to start or supply payload data record event triggers docid\ srdglavepyy1q ywleu9m create, update, or delete on selected applications or records schedule triggers docid\ gvxozitxe2rrvlvelmrav time based or cron style runs playbook button triggers docid\ dptsg wedhn7c1besykr9 users start a run from the canvas or from an application flow event trigger docid 7f7wq vukmtkdvanqilv6 another flow or playbook activity drives execution (orchestration between flows) 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 the playbook button triggers docid\ dptsg wedhn7c1besykr9 type is also available via applications 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 docid\ fngazwp7nqsnvsudl8nbh 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 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 docid\ fngazwp7nqsnvsudl8nbh — configure offset, playbook, and flow configuring playbooks docid\ iqsgpto 17szz7k8ktrai — playbook configuration overview schedule triggers docid\ gvxozitxe2rrvlvelmrav — recurring or cron schedules (different from datetime field trigger)