Integrations
Connect your systems.
Zentra is designed to sit beside the systems you already run. It receives events, adds context, and acts back through the same connections.
01Integration architecture
Sources in. Signals, workflows and outcomes out.
The systems below are illustrative categories. Connector availability will be published here as each one is built.
- Ingest
- Normalise
- Signal
- Context
- Workflow
- SignalsMeaningful events with priority
- WorkflowsCoordinated response, audited
- OutcomesVerified results and analytics
Payments · Settlements, refunds, disputes · via Webhook
| System category | Connection mode | Status |
|---|---|---|
| CRM | Webhook / API | Planned |
| ERP | API / Connector | Planned |
| Support | Webhook | Planned |
| Payments | Webhook | Planned |
| Internal apps | API | Planned |
02Connection flow
From connection to action.
- 01
Connect
Choose webhook, API or connector and add credentials as secrets.
- 02
Ingest
Events are validated, deduplicated with an idempotency key and timestamped.
- 03
Normalise
Fields are mapped to one event shape with source attribution.
- 04
Process
Signals are identified, context is gathered and policy is evaluated.
- 05
Act
Workflows call back into connected systems and record the result.
03Ways to connect
Webhooks, API, connectors.
Webhooks
Systems that can call a URL push events to a Zentra endpoint. Deliveries are logged and can be replayed.
POST → /api/v1/events (example)
Events API
Send events from your own services, and read signals and outcomes back. Authenticated with scoped API keys.
Authorization: Bearer … (example)
Connectors
Managed connections for common systems, listed on this page only once they exist.
Status: planned
Sample data is used throughout this site.