---
title: Orchestration
slug: orchestration
docTags: 
createdAt: 2026-02-09T04:30:30.000Z
---

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:

1. **Model the outcome** — What record or external state should change? What trigger reflects the real world?
2. **Create or open a playbook** — [How to Create a Playbook](docId:0-KvG5p4LTHw75ItmpUWp).
3. **Add triggers** — [Triggers](docId\:SEDgtHtXrZuOHZSUvHAD4).
4. **Add actions** — [Native Actions](docId\:rBn1ysy4kRUWYWmpwbyGa), [Record Actions](docId\:j6eUvk5LaYMULE_3t1nOv), and connector actions from **[Connectors](docId\:vuockVnhiDx3w01LtDMno)**.
5. **Wire inputs and outputs** — Inputs, Outputs, Discovered Outputs and Testing (use the **Action Configuration** folder for the full set).
6. **Validate in the Test Console** — [Test Console](docId:1D0fiftjsdox88PVpK5fS).
7. **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)
8. **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                                  |