Platform · Module
Integration Hub
Certified connectors with checkpoints, replay, signed webhooks and governed writes
Integration Hub connects One3 to external systems through certified connectors built on a Connector SDK that enforces a reliability standard. Mappings write only through the owning module's Actions.
Connectors with a reliability standard
Every connector is built on the Connector SDK, whose manifest declares auth, scopes, provider verification facts, rate limits, sync mode, checkpoint, replay, freshness target, reconciliation, webhooks, schema drift handling, degraded mode, classification and licence terms. A connector that cannot state these cannot ship.
Connections and syncs
Connections support OAuth 2.0, API key and basic auth, with credentials in a cloud KMS secret store, token refresh and expiry alerts. Sync jobs run full, incremental or webhook-plus-reconcile, with checkpoints so they resume after failure. Inbound webhooks are signature-verified, deduplicated by event id and backed by a dead-letter queue with redrive. From Wave 1, tenants subscribe to One3 events through outbound webhooks with HMAC signatures, retries and a delivery log.
Governed writes
Field mappings, value transforms and owner mappings write only through the owning module's Actions, so integration data gets the same validation, permissions and audit as anything else.
Year-1 connectors
The plan prioritises Gmail, Google Sheets, a generic webhook, the WhatsApp Business Platform, Slack and Teams notifications, HubSpot for migration, Meta Ads, Google Ads and Search Console, Microsoft Graph, a payment gateway and a GSP. All access terms are recorded in the Fact Register and verified.
Wave 2
Schema drift detection quarantines unknown fields. Degraded mode serves cached data with a staleness label and queues writes for re-approval. A field-mapping agent and a sync-error fixer make proposals, never auto-applied. Premium connectors carry an add-on entitlement and sync-volume metering. Agencies see connections across sub-accounts with bulk re-auth reminders. Knowledge connectors sync permissions. An OAuth app broker, a generic trigger layer and nightly conformance runs are also planned.
India Stack connectors through licensed partners, such as GSP e-invoice and e-way bill and UPI payment links, are planned from Wave 2, with Account Aggregator, DigiLocker and Aadhaar eSign later (all to verify). Custom connectors via SDK and a Connector Factory follow in Wave 3.
Features
What Integration Hub includes
Connector SDK
Manifest declares auth, scopes, rate limits, sync mode, checkpoint, replay, freshness, drift, degraded mode and licence. W0.
Secure connections
OAuth 2.0, API key or basic auth with KMS-backed secrets, refresh and expiry alerts. W0.
Resumable sync jobs
Full, incremental or webhook-plus-reconcile with checkpoints. W0.
Signed inbound webhooks
Signature verification, dedupe by event id, dead-letter queue and redrive. W0.
Outbound webhooks
Subscribe to One3 events with HMAC signatures, retries and delivery log. W1.
Year-1 connector set
Gmail, Sheets, webhooks, WhatsApp, Slack, Teams, HubSpot, Meta Ads, Google Ads, Search Console, Microsoft Graph, payments, GSP (to verify). W1–W2.
Mappings via owner Actions
Field, value and owner mapping that write only through module Actions. W1.
Schema drift and degraded mode
Quarantine unknown fields; serve cached data with staleness labels; queue writes for re-approval. W2.
Field-mapping agent and sync-error fixer
Proposals with confidence and reasons; never auto-applied. W2.
Premium connectors
Add-on entitlement and sync-volume metering. W2.
Agency connection view
Connections across sub-accounts with bulk re-auth reminders. W2.
OAuth app broker and conformance runs
One3 or tenant client IDs, secret rotation and nightly contract tests feeding health scores. W2.
India Stack connectors
GSP, UPI links first; Account Aggregator, DigiLocker and eSign later, through licensed partners (to verify). W2–W4.
Custom connectors and authority modes
SDK-built connectors with conformance tests; observe, assist or One3-primary modes per connection. W3.
Workflow
Connect Google Sheets for import
- 1
Admin starts an OAuth connection with read-only scope.
- 2
The sync job runs with checkpoints.
- 3
Mappings are reviewed and approved.
- 4
Rows are written through the target module's Actions.
- 5
Health and freshness appear in Connector Health Center.
AI
AI skills and Digital Employees
Field-mapping agent
Suggests mappings with confidence and reasons; an admin approves. W2.
Sync-error fixer
Classifies errors and proposes re-auth, mapping changes or data corrections. W2.
Digital Employees that use this module
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Do integrations bypass One3 permissions?
No. Mapped data is written only through the owning module's Actions, with the same validation and audit.
What happens if a provider is down?
Degraded mode, planned for Wave 2, serves cached data with a staleness label and queues writes that need re-approval after recovery.
Are all connectors free?
Most connectors are included. Premium connectors are a paid add-on with sync-volume metering.
See Integration Hub in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.