Product
Organization integrations shell, planned external connections, and current boundaries.
Integrations is the organization-scoped home for connecting CentraKit to external systems.
The organization integrations page is the marketplace for connecting CentraKit to external systems. Provider-specific integrations are surfaced from the product area that owns them when the corresponding integration is implemented.
The first-party Webhooks tile (webhooks) manages incoming endpoints and outgoing destinations. Workflows bind trigger.webhook to an incoming endpoint and action.webhook to an outgoing destination. Tokens and secrets live in domain tables, not graph JSON or installation metadata. Stripe, WhatsApp, and Resend provider webhooks stay on their owning domain routes.
Likely integration categories include:
suppliers and product_supplier_links already hold source / external_id join keys. A later vendor integration should add catalog-owned supplier_connections (credentials via Vercel Connect or domain secrets), register integration_installations.domain_kind = supplier_connection, sync catalog SKUs onto product links, and send purchase requests from the product’s preferred supplier. Task materials already expose a mailto “order from supplier” fallback.Each integration should have a clear ownership boundary for credentials, webhooks, sync state, and user-facing status. Avoid storing provider-specific channel identities in generic contact-method tables. Supplier API credentials stay off suppliers and on the owning connection tables, the same split Agenda uses for Google Calendar.