Control center
Integrations walkthrough
Integration routes group ERP, WMS, TMS, customs, EDI/ASYCUDA, FIZ-FCZ, webhook, auth, agent mesh and health surfaces. Several leaf pages explicitly state that their live data is not connected; these are status/design surfaces, not proof of active credentials, deliveries or synchronization.
Key routes
- Integration overview
Browse integration domains and entry points.
- ERP
Open ERP connector surfaces.
- TMS
Open transport connector surfaces.
- WMS
Open WMS integration surfaces.
- EDI / ASYCUDA
Review EDI, segment and ASYCUDA screens.
- Webhooks
Open webhook delivery and subscription routes.
- Health
Open the integration health view.
Prerequisites and seed data
- Sign in to the tenant whose integrations you are reviewing.
- An integration needs an external endpoint/credential and environment configuration before it can exchange data; no secrets or connection should be inferred from a screen shell.
- Use test/sandbox endpoints and approved secret-management practice when validating a connector.
Primary workflows
Inspect a connector surface
Navigate to the relevant integration and verify the current connection state before relying on it.
- Open the integration overview and select the system involved. Integration overview
- Review its route and confirm whether the page reports connected live data or an explicit unconnected status. ERP
- Use the health route as an overview, not as a connectivity guarantee when it has no live source. Health
Review EDI configuration surfaces
Inspect the existing mapping and message layout routes; they may be scaffolds rather than persisted editors.
Investigate webhooks
Use the route family to find the delivery/subscription surfaces while accounting for their current disconnected state.
- Open webhook overview. Webhooks
- Review subscriptions and deliveries; the current pages identify their data as not connected. Subscriptions
- Do not treat an empty table as proof of no deliveries until a live data source is connected. Deliveries
Concepts
- Connector
- An integration endpoint/configuration linking TradeOps with an external platform; it is operational only when configured and exercised.
- EDI mapping
- A mapping between external message segments and the application’s data contract.
- Webhook delivery
- A delivery attempt of an event to a subscribed endpoint; the delivery page explicitly states its data is not connected.
- Secret
- Sensitive integration credential; manage only through an approved secret store and never paste into walkthrough content.
Data sources and implementation status
- The backend mounts agentMesh, customs, edi, erp, fizFcz, tms, webhook and WMS external routers under the integration namespace.
- The integration route pages have no direct tRPC calls in this route tree; several leaf pages explicitly report that live data is not connected.
- Router registration is in backend/src/trpc/trpc.router.ts; integration implementation files are under backend/src/integration/.
Permissions
- The route pages do not call integration tRPC procedures directly. If a composed component later invokes one, inspect its applied middleware; shared CRUD handlers do not add authentication or role checks by themselves.
- Credentials and API keys are sensitive; do not expose them in logs, issue reports, or walkthrough content.
- Role enforcement belongs to the backend procedures. Confirm specific grants before editing connector settings or triggering external traffic.
Troubleshooting
| Symptom | Check | Where to look |
|---|---|---|
| Health grid or webhook tables are blank. | These pages currently pass empty collections or state that live data is unconnected; this is not evidence of zero system events. | app/(app)/integration/health/ and webhook/ |
| ERP/TMS/customs page shows an integration shell only. | The leaf page explicitly marks live data as unconnected; inspect the backend integration router for actual connection implementation. | app/(app)/integration/ and backend/src/integration/ |
| A credential cannot be used. | Verify approved secret provisioning and connector setup; do not paste secrets into app logs or walkthrough pages. | backend/src/integration/ and the organization’s secret-management configuration |
Where things live
- Integration routes
- app/(app)/integration/
- Integration router modules
- backend/src/integration/
- tRPC registration
- backend/src/trpc/trpc.router.ts
- Explicit disconnected state: ERP
- app/(app)/integration/erp/
- Explicit disconnected state: webhooks
- app/(app)/integration/webhook/
Audience: developer · Last reviewed: