The control plane and the connector pack
Two more waves of platform work shipped: tenant API tokens that resolve into the permission model (the control plane), and a connector pack — Google Ads, GA4, HubSpot, Gmail, Slack — on the durable, incremental ingestion pipeline.
On the heels of the platform-hardening wave, two more pieces landed —
the control-plane credential and the start of the connector pack (v1.30–v1.32).
The control plane: tenant API tokens (v1.30)
For an app or a client integration to drive Vocion — start work, approve, manage scopes — it needs a
credential. Tenant API tokens (vcn_live_<id>_<secret>, SHA-256 at rest, shown once) do that, and
crucially they resolve into an authz principal: a token carries a role + grants + org scope, so any
mutation it makes routes through the same permission model and review queue as everything else.
Authentication and authorization are one path, not two.
The connector pack (v1.31–v1.32)
A platform that can't touch your data is a demo. So we shipped the first connectors, all on the durable ingestion pipeline:
- HubSpot — CRM contacts, deals, companies.
- Google Ads — campaign performance by day.
- GA4 — sessions, conversions, bounce rate by date + landing page.
- Gmail — messages.
- Slack — channel history.
Each is incremental (fetch only what changed since the last watermark), resumable (a failed sync picks up where it left off), and client-scoped — ingested data inherits the access boundary, so one workspace can serve many clients without leakage. Connectors stay narrow: they yield records; the runtime does the chunking, embedding, dedup, and scoping.
Why these
They're exactly what our two reference deployments need: Google Ads + GA4 for PPC/CRO reporting, HubSpot + Gmail + Slack for revenue operations. Building toward real deployments is what tells us the platform is ready — see the connectors doc for the current set and how sync works.
More connectors and the rest of the control plane (write-API routes, MCP over HTTP) are next.