Configuring Playbooks

use playbook configuration to define how a playbook starts, what it runs, and how flows connect most trigger types are added from the solution builder canvas datetime field triggers are an exception they are created from a date/time field in application builder and then appear on the selected flow as a system managed trigger choose your path i want to… start here understand trigger types triggers docid\ sedgthtxrzuohzsuvhad4 schedule a flow from a date/time field value select fields and assign field properties https //docs swimlane com/select fields and assign field properties#datetime field triggers add a datetime field trigger on the canvas not available — configure from application builder field settings; see triggers https //docs swimlane com/triggers#datetime field trigger see which triggers can share a flow flow sharing rules https //docs swimlane com/triggers#flow sharing rules review missing inputs, outputs, errors, required, sensitive, type, or discovered outputs review missing action properties /#review missing action properties use cron or recurring schedules schedule triggers https //docs swimlane com/schedule triggers start from a record create, update, or delete record event triggers https //docs swimlane com/record event triggers start from an external http call webhook triggers https //docs swimlane com/webhook triggers start from a button playbook button triggers https //docs swimlane com/playbook button triggers chain flows together flow event trigger https //docs swimlane com/flow event trigger datetime field triggers and scheduled playbook flows starting in turbine 26 3 0 (sla tracking phase 1), you can run a playbook flow at a specific time based on a record date/time field in application builder , select a date/time field under advanced → trigger playbook , click configure set offset , unit ( minutes or hours ), and the target playbook / flow save the dialog, then save the application turbine adds a datetime field trigger to the selected flow the trigger details are read only on the canvas and point back to the field settings when records are created or updated, turbine schedules, reschedules, or cancels runs so the flow fires at the field value ± offset (maximum absolute offset 7 days ) when the datetime field trigger fires, the playbook receives the full record (not tracking id only), so you can map field values from the trigger output like a record event trigger a datetime field trigger cannot share its flow with a playbook button, correlation, or another datetime field trigger playbook buttons and correlation may share a flow see flow sharing rules https //docs swimlane com/triggers#flow sharing rules deleting a playbook or flow that is linked to a date/time field trigger configuration clears that configuration from the application field and cancels outstanding schedules confirm the impact warning before you proceed full configuration and lifecycle details select fields and assign field properties https //docs swimlane com/select fields and assign field properties#datetime field triggers and triggers https //docs swimlane com/triggers#datetime field trigger review missing action properties starting in turbine 26 3 3 , canvas walks you through actions whose inputs , errors , or outputs schema references are missing connector actions, http, script, transformation, emit event, create variables, update variables, record actions, condition, and loop can appear in the review playbook and component runs do not change you review the flagged settings, then save the playbook canvas does not include these in the walkthrough parallel and action group wrappers read only canvas nodes actions inside an expanded component (review those on the component canvas) on a component, canvas reviews only the first playbook on that component what canvas flags as missing the coachmark names only the sections that are broken on that action, in this order inputs , errors , outputs what is missing what to review inputs required , sensitive , and type on highlighted input properties outputs required , sensitive , type , and discovered outputs errors required and sensitive on error properties discovered outputs re test the action, add the outputs again, and mark sensitive as needed this guidance appears only when outputs is broken create, update, or upsert record selected record fields re select the application and the fields if any are missing these actions do not use required or sensitive delete record standard inputs review ( required and sensitive ) if no section is identified, the coachmark says review configuration for missing required, sensitive http can appear in the walkthrough http does not use the json editor type recovery used on other actions start and pause the review open the playbook on the canvas if actions need review, canvas opens configuration details need to be reviewed the dialog says check if any inputs or outputs should be marked as required or sensitive check if any discovered outputs are missing to recover them, re test the action, re add discovered outputs, and mark them sensitive as needed configuration appears to be missing this does not affect playbook or component execution it only impacts editing and the run document view click proceed to start, or click cancel to pause cancel keeps resume available on each action, the coachmark uses one of these messages review inputs for missing required, sensitive review errors for missing required, sensitive review outputs for missing required, sensitive, and discovered outputs review inputs and errors for missing required, sensitive review inputs and outputs for missing required, sensitive, and discovered outputs review inputs, errors, and outputs for missing required, sensitive, and discovered outputs please verify the selected record fields if any fields are missing, re select the application and the fields click configure or edit , or click skip configure opens action properties edit opens the side panel action broken section coachmark button condition any edit while loop inputs (delay, duration, limit) configure while loop outputs or errors edit for each inputs (contains sensitive data) edit for each outputs configure other actions any configure if an action has more than one broken section, canvas prefers configure when any section uses configure 6\ if more than one action remains, use the coachmark arrows to move between actions 7\ while the review is active, click pause in the canvas toolbar (next to test and save ) 8\ after pause , skip , cancel , selecting another action, or adding or pasting an action, the toolbar shows resume 9\ click resume the same configuration details need to be reviewed dialog appears click proceed or cancel review highlighted properties open the action missing properties have a yellow highlight read the toast titled configuration details need to be reviewed for most actions, the toast includes review the highlighted properties as configuration appears to be missing check if any of them should be marked as required or sensitive set the type where the blue type icon is available property types can only be changed before clicking apply check if any discovered outputs are missing to recover them, re test the action, re add discovered outputs, and mark them sensitive as needed this does not affect playbook or component execution it only impacts editing and the run document view on a component action, the toast omits required , sensitive , and discovered outputs when you open edit (side panel, while loop panel, or loop outputs), the toast is configuration appears to be missing check if any inputs or outputs should be marked as required or sensitive if canvas already knows which section is broken, that toast uses the same review inputs / errors / outputs wording as the coachmark on create, update, or upsert record, the toast says please verify the selected record fields if any fields are missing, re select the application and the fields set required and sensitive on each highlighted property as needed where a blue type icon appears, set type hover text set the property type you can do this only before you click apply if discovered outputs are missing, click test , add the discovered outputs again, and mark sensitive where needed click apply in the configuration details need to be reviewed confirm dialog, verify the following, then continue please verify each highlighted property's type and its required and sensitive options properties with a changeable type will default to object if left unchanged this cannot be updated later some discovered outputs may also be missing to recover them re test the action, re add discovered outputs, and mark them sensitive as needed once changes are applied, the highlights and warning messages will no longer appear after every flagged action is reviewed, canvas shows configuration review complete all flagged configuration has been reviewed and save your changes so the updated settings are persisted click save to persist the playbook, or click close to stay on the canvas without saving you can still update required and sensitive later you cannot change type after apply if you pause the review and copy an action or flow before you finish, later review repairs only the original action the pasted action can stay out of the coachmark list finish the review on the original action before you copy, or delete the pasted action and copy again after the review is complete related topics triggers docid\ sedgthtxrzuohzsuvhad4select fields and assign field properties docid\ fngazwp7nqsnvsudl8nbhapplication builder docid 6q6y4 02l v2khn80gmo5organizing playbook in the canvas https //docs swimlane com/organizing playbook in the canvascreate and modify playbooks with hero ai https //docs swimlane com/create and modify playbooks with hero ai