Connectors

Connectors turn what happens in your tools into events in your log. They follow one contract: emit events, propose claims, never touch projections. Everything a connector brings in flows through the same adjudication path as everything else, so provenance is never lost at the door.

Connector-derived content is treated as data, never as instructions. Message bodies and page content are wrapped as untrusted before any model sees them, which is the structural defense against prompt injection.

Gmail / Google Workspace

Emits email.received and email.sent events with participants. Email is the richest record of business relationships; from it Wavetable proposes people, companies, and the threads on each record page.

Stripe

Emits customer, invoice, and subscription events. Revenue arrives with deterministic identity keys, so lifetime value, plan, and payment history attach to the right person without guesswork.

Site script

A first-party JavaScript snippet, about 2KB, that you paste into your site. Emits pageviews, form submits, campaign parameters, and a first-party device id. This puts content, traffic, and conversion in the same graph as email and revenue, which makes attribution a query instead of a product you buy.

Google Calendar

Emits scheduled and held meetings with attendees. Beyond the obvious record enrichment, temporal co-occurrence is strong fuel for identity resolution.

Twilio

Emits received and sent SMS. For many small businesses, texting is where the actual customer relationship lives.

CSV import

The migration on-ramp. Upload a file, map columns to fields with a human-checked mapping step, and rows enter as bulk claim proposals, with the same provenance and adjudication as everything else. See importing data.

Resend (outbound)

Outbound email delivery for approved sends. Outbound is not a connector in the ingest sense: nothing leaves Wavetable without a capability minted by an approved policy, and gated sends wait in your Inbox as drafts first.