Sources that sync themselves
Vocion Team
A source's schedule now actually fires — runSync runs inside a durable Temporal Workflow on a Schedule, so connectors keep their knowledge fresh on their own cadence, crash-safe and incremental.
4 posts
A source's schedule now actually fires — runSync runs inside a durable Temporal Workflow on a Schedule, so connectors keep their knowledge fresh on their own cadence, crash-safe and incremental.
The Drive connector — Docs, Sheets, Slides, and text files exported into scoped, retrievable knowledge — completes the connector set the two reference deployments run on.
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.
The credential vault is now wired into the ingestion pipeline — a connector's OAuth/API credentials are stored encrypted-at-rest per tenant and resolved at sync time, so the connector pack can actually authenticate.