Orchestration Overview

orchestration overview 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 3h4uaq7pbxjvmdlqlmhhy building blocks reusable elements such as connectors, components, assets, and webhooks see building blocks monitoring review health and run information for orchestration see docid 92ewozfzdide7pp5t5m5d reference schemas and technical references for interoperability see docid 9xbsstsojlm9 wdiim6d5 classic playbooks legacy content kept separate see docid 4dm50bi5gulqpvzvn0z7u recommended path create a playbook docid\ hvrzctyqyv7h6oz3bb0wo learn the canvas docid 3h4uaq7pbxjvmdlqlmhhy configure triggers docid\ krkfgjbkiuwgaqdcnlzug use actions docid\ qug5k0u xtt24rwxryxo5 publish playbooks docid\ gy3rshos3tipnkwfbjqc3 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\ z n fzu9tdqmf3h5dkpxy monitor runs in docid 92ewozfzdide7pp5t5m5d 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