Architecture
Integrations
EntiHub helps you move from "master data exists" to "master data is actively used" across apps, pipelines, and analytics.
Integration model in one view
| Pattern | Best for | Typical latency |
|---|---|---|
| REST API | Application reads/writes, custom workflows, service integrations | On-demand (request/response) |
| Webhooks | Event-driven notifications to downstream systems | Near real-time |
| Data Loads | Controlled onboarding/sync from source systems | Batch or scheduled |
| SQL/Views for BI | Analytics and reporting consumption | Query-time / refresh-time |
REST API (system-to-system backbone)
- Use API when applications need authoritative master records directly in operational flows.
- Strong fit for ERP/CRM middleware, custom portals, and enrichment services.
- Also supports automated governance workflows through CI/CD and CLI-assisted operations.
Webhooks (push when something important changes)
- Use webhooks when approved changes must trigger downstream actions immediately.
- Typical examples: update ERP vendor data, notify CRM, trigger ticket/process orchestration.
- Great for reducing polling and keeping operational systems synchronized with governed master data.
Data Loads (controlled source onboarding)
- Use Data Loads when onboarding legacy SQL sources in repeatable steps.
- SQL-driven definitions make source-to-entity upsert flows easier to version and re-run safely.
- Best for phased migration where quality controls and traceability are required.
Analytics consumption (trusted data where BI already runs)
- Consume master data directly through SQL tables or curated consumption views.
- Power BI and other analytics tools can read governed dimensions without manual export steps.
- Historized entities support reproducible as-of analysis when required.
Recommended rollout order
- Step 1: connect one critical consumer via API or SQL view.
- Step 2: add webhook notifications for high-impact change events.
- Step 3: onboard additional systems with Data Loads and automation.
- Step 4: standardize CI/CD and operational runbooks with CLI/API patterns.
Why this works well with EntiHub
- One platform combines model, governance, and integration in a single lifecycle.
- Practical controls (approvals, audit, RBAC) keep integration quality high without heavy overhead.
- YAML + API + CLI make integrations repeatable and automation-ready.
See automation with AI agents and CLI | See core concepts | Back to Learn center