GRIP OS
GRIP OS
CAUGIA · CONNECTOR LIBRARY
Pull-sync from your stack into the diagnostic. Push outbound from the action plan into the tools your team already lives in.
Daily at 06:00 UTC, the connector dispatcher walks every active inbound source: CRM, billing, product analytics, mailbox, helpdesk, customer success. Each connector returns a SignalBatch into the workspace. Sophie scores 12 pillars from real signal, not from the assessment alone.
When an action lands or a constraint advances, an event-driven dispatcher fires the push request to every configured destination. An Asana push lands as a task. An Atlassian push lands as a Jira issue. A Clay push appends a row. The mapping is deterministic.
The push registry tags every handler into one of 25 categories that mirror how operators actually structure the GTM stack. Configure only the destinations your team uses; ignore the rest.
Hard-active handlers reach a live destination API and create the artefact end to end. Soft no-op handlers ship the same configuration UI but the destination API is currently gated, enterprise-only or pending vendor partnership. The audit log captures the call either way. As soon as we obtain partner credentials, the handler graduates to hard-active without changing the slug or the saved configuration. Today the split is 86 hard-active and 386 soft no-op, which reflects how many vendor APIs sit behind partner gates rather than how many tools we plan to support.
OAuth refresh tokens and API keys are stored in a service-role-only Postgres table with envelope encryption. The encryption key lives in the Supabase secrets store, separate from the database, so a database dump alone does not expose the credentials. The connector chassis fetches the credential at sync time, decrypts it in memory, performs the source call, and discards the decrypted value before returning. The credential never lands in a log line, an error message or a response body. Audit log entries record every connect, push, and disconnect event with actor and timestamp.
The connector library is large by design because the diagnostic is only as good as the signal coverage feeding it. Most workspaces start with the CRM, the billing source and one product-analytics source and add others as the diagnostic narrows.