Skip to content

Connectors overview

Connectors let your published site talk to external services — get a Telegram DM on every order, log leads to Google Sheets, store submissions in Notion, play your Twitch stream, read aloud with ElevenLabs, and more. You add your credentials once in Settings; they’re encrypted on the server and never end up in your site’s code.

  1. Configure once — in Settings → Connectors, pick a service and paste its credentials (e.g. a Telegram bot token). Secrets are encrypted and stored server-side.
  2. Wire it in chat — tell the AI what should happen: “send me a Telegram message when someone submits the contact form.”
  3. It runs safely — when the trigger fires on your live site, the call goes through a secure Genesis relay that injects your secret server-side and calls the service. Your keys never touch the browser.

A catalog grid of services, each card showing its official brand mark, a one-line description, its category, and a docs link. Click a card to open its setup form — fields come straight from what that service needs (a token here, a chat ID there), with hints on where to find each value. Saved connectors show Configured with an enable/disable toggle; delete removes it cleanly.

Already-saved secrets stay hidden — to change other settings (like a chat ID) you can leave the secret field blank and it keeps the existing value.

Describe the trigger and Genesis wires the connector call into it. Just describe it — no special syntax needed. For example:

  • “DM me on Telegram when someone submits the contact form”
  • “notify my WhatsApp number on a new order”
  • “save each submission to my Notion leads database”

If the connector isn’t configured yet, Genesis still wires the call and tells you to finish setup in Settings → Connectors — so the page never breaks, and it starts working the moment you add your credentials.

  • Enter once, stays on the server. Credentials are encrypted at rest and only decrypted in memory, for the moment a call is made.
  • Never in your site. Your published build contains no secrets — every call is relayed through Genesis.
  • Locked down. Each connector can only reach its own service (no redirection elsewhere), and calls are rate-limited per visitor to prevent abuse.
  • Some connectors (Supabase, Firebase, AWS S3) use a public config by design — there the security comes from that service’s own rules (RLS, Security Rules, bucket policy), and any truly sensitive admin key stays server-side.

Each of these has its own page with setup steps, example prompts, and use cases:

ConnectorCategoryIn one line
TelegramMessagingDM a chat/channel via a bot
WhatsAppMessagingSend WhatsApp messages (Meta Cloud API)
NotionProductivityCreate entries in a Notion database
Google SheetsProductivityAppend rows to a spreadsheet
SupabaseDataYour own Supabase — database, auth, storage, realtime
FirebaseDataYour own Firebase — Firestore, auth, storage
AWS S3FilesList, upload, download bucket files
TwitchMediaEmbed your live stream + chat
ElevenLabsAIText-to-speech narration

Nine more services, each wired the way its own API expects:

ConnectorCategoryIn one line
SlackMessagingPost to a channel — order alerts, form submissions, anything
DiscordMessagingPost to a server channel
ShopifyCommerceRead your store’s products and orders
AirtableProductivityCreate and read records in a base
Cal.comSchedulingBooking and availability on your page
Google ReviewsSocial proofShow your Google Business reviews
TrustpilotSocial proofYour Trustpilot rating — ships as a widget, because Trustpilot walls its API off
YouTubeMediaPull a channel’s videos onto the site
SpotifyMediaShow playlists, albums, or episodes

Pick a connector above for its setup steps and example prompts.