Connectors and channels

If the data layer is about what an AI can read and do inside your app, this page is about the bridges outward: syncing with external providers (Google Calendar, Stripe) and — the question founders ask most — serving customers over messaging channels like WhatsApp.

Part of this is already in production. Part of it is roadmap, and we say plainly which is which. For the full list of providers in the catalog (with each one's status), see the Integrations page.

The connector spine

There's a real connector contract in @fayz-ai/core (packages/core/src/integrations): Connector and ConnectorDefinition. A connector declares:

An auth mode — oauth, api-key or mtls.
Capabilities — what it knows how to sync.
testConnection and sync — test the credential and pull/push data.

A plugin publishes connectors through the manifest's connectors field (the plugin becomes an addon of a host). The shell ships a shared ConnectorsHub in settings, where users connect and manage providers. The heavy sync work runs in Supabase Edge Functions — the data plane lives in the backend, not in the browser.

Think in two planes: the control plane is the /settings UI (connect, test, choose what to sync); the data plane is the edge function that actually performs the sync. The contract in @fayz-ai/core stitches the two together.

Two connectors that already exist

This isn't theory — two POCs have shipped:

Google Calendar

In plugin-agenda: OAuth, a calendar picker and event sync. It lives in src/integrations/google-calendar. It's the canonical example of a plugin-native connector.

Stripe

In plugin-courses: a payments connector in src/connectors/stripe.ts. It shows the same contract applied to a billing provider.

Both follow the same ConnectorDefinition — it's the pattern your own plugin replicates to talk to any external provider.

Messaging channels — and WhatsApp

Here's the part founders press on: how these products reach WhatsApp. The honest answer has two halves — the foundation that exists and the milestone still to come.

What exists: the omni-channel inbox

plugin-conversations is an experimental omni-channel inbox. The channel enum already includes whatsapp as a label, and the plugin declares the aiTools listConversations (read) and sendMessage (persist). In other words: the structure for an inbox, threads and AI tools to read and reply is already modeled.

Experimental