# Connectors overview

> Connect your site to external services — Telegram, WhatsApp, Slack, Discord, Notion, Airtable, Google Sheets, Shopify, Supabase, Firebase, AWS S3, Twitch, YouTube, Spotify, Cal.com, Google Reviews, Trustpilot, ElevenLabs — with your API keys kept safe on the server.

Source: https://knowledge.estage.com/connectors/
Part of the ESTAGE knowledge base (https://knowledge.estage.com). Full corpus: https://knowledge.estage.com/llms-full.txt

---
**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.

## How it works

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.

## The Settings → Connectors tab

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.

## Wiring it from chat

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.

## Security

- **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.

## What's available

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

| Connector | Category | In one line |
| --- | --- | --- |
| [**Telegram**](/connectors/telegram/) | Messaging | DM a chat/channel via a bot |
| [**WhatsApp**](/connectors/whatsapp/) | Messaging | Send WhatsApp messages (Meta Cloud API) |
| [**Notion**](/connectors/notion/) | Productivity | Create entries in a Notion database |
| [**Google Sheets**](/connectors/google-sheets/) | Productivity | Append rows to a spreadsheet |
| [**Supabase**](/connectors/supabase/) | Data | Your own Supabase — database, auth, storage, realtime |
| [**Firebase**](/connectors/firebase/) | Data | Your own Firebase — Firestore, auth, storage |
| [**AWS S3**](/connectors/aws-s3/) | Files | List, upload, download bucket files |
| [**Twitch**](/connectors/twitch/) | Media | Embed your live stream + chat |
| [**ElevenLabs**](/connectors/elevenlabs/) | AI | Text-to-speech narration |

### Also in the catalog

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

| Connector | Category | In one line |
| --- | --- | --- |
| **Slack** | Messaging | Post to a channel — order alerts, form submissions, anything |
| **Discord** | Messaging | Post to a server channel |
| **Shopify** | Commerce | Read your store's products and orders |
| **Airtable** | Productivity | Create and read records in a base |
| **Cal.com** | Scheduling | Booking and availability on your page |
| **Google Reviews** | Social proof | Show your Google Business reviews |
| **Trustpilot** | Social proof | Your Trustpilot rating — ships as a **widget**, because Trustpilot walls its API off |
| **YouTube** | Media | Pull a channel's videos onto the site |
| **Spotify** | Media | Show playlists, albums, or episodes |

:::note
Where a provider doesn't offer real API access, the connector says so rather than pretending —
Trustpilot is the widget case above.
:::

:::note
Connectors are different from [Webhooks](/capabilities/webhooks/): a webhook just POSTs your
data to a URL you paste (Zapier/Make), while a connector is a managed integration with a
specific service, with your credentials vaulted and the call relayed for you.
:::

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