Admin Reference
Connected Systems Route Reference
Understand the shared hub for connections, staged imports, API keys, and webhooks.
Before you start
- Connected-system features are enabled and you need one workspace for integrations, imports, and credentials.
Expected outcome
You can use Connected Systems as the parent hub instead of hunting across older standalone routes.
What this route is for
Connected Systems is the customer-facing hub for external connections, staged imports, machine credentials, and outbound webhooks.
Visibility and capability notes
| Item | Details |
|---|---|
| Route id | connected-systems |
| Visibility | Customer-facing when connected-system capability is enabled. |
| Capability notes | This route is a hub. It embeds several desks that also have legacy standalone entrypoints. |
| Direct inbound | Shell nav, dashboard integration summary, import buttons from CRM or register desks, and redirects from older standalone routes. |
Main tabs, embedded desks, and controls
| Surface | What it does |
|---|---|
connections | Embedded integrations desk for connection management. |
imports | Staged import workspace for customer, register, and work-order datasets. |
api-keys | Embedded API key management. |
webhooks | Embedded webhook management. |
| Header action | Changes with the active section so the route always opens the right create flow. |
Key actions
- Connect or edit an external system.
- Run staged imports.
- Create API keys.
- Create webhook endpoints.
- Stay inside one hub while switching between connection-related concerns.
Filters and URL state
| Param | What it controls |
|---|---|
section | Active connected-systems desk |
| Preserved section params | Connection, import, key, or webhook ids are preserved when switching or reopening the route |
- The hub preserves section-specific params rather than flattening every child workspace into one global filter set.
Outputs and side effects
- Creates and updates live connections.
- Runs staged imports for datasets such as
customers-sites,systems-assets, andwork-orders-tasks. - Issues API keys and webhook endpoints.
- Pushes external-system side effects into the rest of the product.
Inbound links
- Shell
Connected Systemsnavigation. - Dashboard integration summary.
- Import buttons from Customers, Sites, Assets, Systems, and Work Orders.
- Redirects from
integrations,api-keys, andwebhooks.
Outbound links
- Mostly route-local section switching
- Embedded desk actions can later open account, site, or operational context indirectly
Indirect handoffs
- Connected Systems is the main boundary between Deucalion and external source systems.
- Many operational questions that look like bad data are really import, sync, or credential issues surfaced here.
Troubleshooting
| Symptom | What to check |
|---|---|
| The route opens in the wrong desk | Check the section param first. |
| An import button lands in the hub but not the right dataset | Confirm the source route passed the expected import dataset context. |
| A legacy link looks broken | Many older entrypoints now intentionally redirect here. |