Orchestration

orchestration helps you automate workflows in turbine using playbooks, actions, and reusable building blocks this section focuses on how to build, configure, and manage automation safely and consistently core concepts playbooks automation workflows made of triggers and actions actions steps inside a playbook (native actions or connector actions) components reusable groups of actions you can drop into multiple playbooks assets stored credentials and key/value pairs used by actions key areas playbooks build end‑to‑end workflows that trigger on events and execute actions start here docid\ dp agnnne2mjjfgtv2lz5 building blocks reusable elements such as connectors, components, assets, and webhooks see building blocks monitoring review health and run information for orchestration see docid\ yxniv85ogqgr6v6hr0b3s classic playbooks legacy content kept separate see solution packages import and export solution packages recommended path create a playbook docid 0 kvg5p4lthw75itmpuwp learn the canvas docid\ dp agnnne2mjjfgtv2lz5 configure triggers docid\ sedgthtxrzuohzsuvhad4 use actions docid\ rbn1ysy4kruwywmpwbyga publish playbooks docid\ ydkkfw8qmknmo6qam06o0 common tasks add a trigger to start a workflow (record event, schedule, webhook, or button) add actions to ingest, enrich, or update data test and debug with the docid 1d0fiftjsdox88pvpk5fs monitor runs in docid\ yxniv85ogqgr6v6hr0b3s best practices keep playbooks small and modular use components for reusable logic store credentials in assets, not in inputs add naming conventions for easier search and maintenance what’s new vs classic canvas playbooks use flows, modern triggers, and the new action configuration experience classic playbooks remain available in the classic section and are not mixed with canvas content