Orchestration
orchestration in swimlane turbine is how you design, run, and observe automation canvas playbooks, triggers, actions, integrations, and operational health this hub maps each area to the topics below so you can go straight to procedures at a glance concept definition playbook a workflow made of one or more triggers and flows of actions on the canvas trigger what starts a run (for example, record change, schedule, webhook, flow event, or button) native action a built in canvas step (records, http, logic, notifications, and so on) connector action a step that calls an external product through a configured connector component a reusable block of canvas logic you can publish and share across playbooks asset stored credentials or values that actions reference instead of hard coding secrets recommended lifecycle follow this order when you are building a new canvas automation model the outcome β what record or external state should change? what trigger reflects the real world? create or open a playbook β how to create a playbook docid 0 kvg5p4lthw75itmpuwp add triggers β triggers docid\ sedgthtxrzuohzsuvhad4 add actions β native actions docid\ rbn1ysy4kruwywmpwbyga , record actions docid\ j6euvk5laymule 3t1nov , and connector actions from connectors docid\ vuockvnhidx3w01ltdmno wire inputs and outputs β inputs, outputs, discovered outputs and testing (use the action configuration folder for the full set) validate in the test console β test console docid 1d0fiftjsdox88pvpk5fs publish or change availability β publish playbooks docid\ ydkkfw8qmknmo6qam06o0 ; to pause or resume without deleting work enable and disable playbooks https //docs swimlane com/enable and disable playbooks operate β orchestration health docid\ yxniv85ogqgr6v6hr0b3s for runs, events, and alerts practices prefer small playbooks and components for reusable branches keep secrets in assets , not in plaintext inputs use consistent names for playbooks and components so search and handoffs stay clear after major changes, test in the test console , then confirm behavior in orchestration health see also topic link use cases and patterns examples and troubleshooting β use cases full documentation map documentation overview hero ai (product wide) hero ai