Automation & integrations¶
Use Danbyte as the source of truth for your automation - feed config data to devices, render configs, and notify other systems when things change.
New to this? Start with the orientation
Danbyte never touches your devices - it stores the intended config and hands the work to a runner you control. The config-drift guide has a "where do I click" map, and Integrations → Automation targets → Guided setup connects your first runner in three steps.
In this section¶
| Page | What it's for |
|---|---|
| Ask Danbyte (chat) | A chat in the top bar that answers questions about your own data, with your permissions. Off by default; runs against a local model if you want nothing to leave the network. |
| Agent access (MCP) | Let an AI assistant read (and optionally change) this tenant's data with the permissions of an API token. Off until you turn it on. |
| Scripts | Write Python that reads and writes Danbyte as you - bulk edits and CSV reports, on a button or a schedule. |
| Config contexts | Attach configuration data to devices/VMs by matching site, role, platform, and more. |
| Export templates | Render objects to text (configs, reports) with templates. |
| Config drift (Ansible/Terraform) | Run an external Ansible/Terraform runner against Danbyte as source of truth; report config drift and sync. |
| Advanced: custom-field-driven playbook | Use a per-device boolean custom field as a feature flag a runner reads from the inventory (e.g. install btop when on). |
| Webhooks | Notify external systems on create / update / delete, signed for verification. |
| Import & export | Move data in and out as CSV / XLSX. |