The job of this console
Pick a connector, finish connection and mapping, run a test, watch sync health. Fix canonical rows when the payload is wrong.
Integrations · Hub
Integration Hub
Launch pad for connectors that write Employee, Project, PurchaseOrder, Task, or time — not a parallel business database.
Scroll to Flowcharts. Scenario: Configure an integration connector.
Connector home
Pipes into records you already own
Integration hub is the door into connectors. They write or read Employee, Project, purchase contracts, tasks, and time — they do not become a second Tracopus.
Integrations → Integration hub
Route
/integrations/hub
Org flag hubEnabled
Integration admin · Admin
Seat at the table
Integration admins and admins with hubEnabled. Business users do not configure pipes from here.
The working rhythm
Hub → connection → map → test → monitor. Return to the hub only to pick the next pipe.
Moments that bring you here
New vendor. After a failed batch. When Sales asks for Salesforce PO import. When HR asks about ZingHR leave.
ⓘ
Pipes, not source
Native leave, timesheet, and PO flows stay protected. Adapters must not invent duplicate source tables.
Flowcharts
1 — Pick a connector then prove a sync
Open a connector, map, test, watch health.
flowchart TD
A[Open Integration hub] --> B[Pick connector]
B --> C[Connections / marketplace]
C --> D[Mapping]
D --> E[Test sync]
E --> F[Sync health]
- 1OpenIntegrations → Integration hub.
- 2ChooseInstalled or marketplace.
- 3MapExternal fields → canonical.
- 4ProveTest sync, then monitor.
Overview
The hub routes to connections, marketplace, adapters, mapping, jobs, and health. Canonical entities remain Employee, Project, PurchaseOrder, Task, TaskActivity, and time. Leave vendor sync must not replace native leave.
How to use
1. Admin API keys are platform
This hub is connectors.
2. Work-time adapters
Generic import/export — not a named vendor WBS store.
3. Persona
Sync must not unmask fields the persona cannot see.