Integrations
The Portal route /integrations is currently a demonstration surface. It renders a provider catalog, example connections, webhooks, delivery logs, and local interaction states from constants in the browser bundle.
What you can inspect
The page demonstrates the intended organization of integration operations:
- Provider discovery by category and status.
- OAuth, API-key, file-upload, and webhook-only connection types.
- Multiple connections for providers that allow them.
- Per-pillar data mappings.
- Connection health, sync timing, and delivery logs.
- Inbound and outbound webhook views.
The displayed providers, connection names, URLs, signing secrets, health values, and event payloads are sample data. Buttons and dialogs update local component state only.
Current limitations
This page does not call Portal API, GraphQL, or MCP integration operations. It does not create a production connection, persist credentials, trigger a real synchronization, or register a webhook. The example whsec_... values do not define an InBlack webhook signature format and must not be used to implement verification.
Use the owning pillar’s reviewed workflow for production connections, such as Accounting’s Stripe connection or Studio’s GitHub and deployment controls. Do not treat a provider’s presence or status on this Portal page as a production support commitment.