# Connectors

How an app talks to Telegram, Google Sheets, email, GitHub, Kaspi, Bitrix24 or any HTTPS API without ever holding a key. The full catalog, with what works today and what does not.

URL: https://docs.qaldy.com/connectors/

A connector is how data enters and leaves a workspace. In the City it is a **gate** on the island's edge; in the console it lives at **Connectors**. An admin pastes a key once; the API seals it to the gate; the gate opens it for one call at a time, adds it to the request and scrubs it from the reply. App code never holds a credential. Every call and every refusal is an audit row.

![The Connectors screen: a card per service with its status, and the connections already in the workspace with their health.](https://docs.qaldy.com/screens/connectors.webp "Connectors in the console. Every card says whether the service works today, is a preview or is planned. Sample workspace.")

## The catalog

This table is read from the same catalog the console shows, so a status here is the status there.

| Service | Group | Status | How you connect | Regions |
|---|---|---|---|---|
| [Kaspi](https://docs.qaldy.com/connectors/kaspi/) | Commerce and payments | [[Preview]] | API key | global, Kazakhstan |
| Ozon | Commerce and payments | [[Planned]] | API key | global, Kazakhstan |
| Shop | Commerce and payments | [[Planned]] | API key | global, Kazakhstan |
| Shopify | Commerce and payments | [[Preview]] | API key | global, Kazakhstan |
| [Stripe](https://docs.qaldy.com/connectors/stripe/) | Commerce and payments | [[Available]] | API key | global |
| Wildberries | Commerce and payments | [[Preview]] | API key | global, Kazakhstan |
| amoCRM | CRM | [[Preview]] | API key | global, Kazakhstan |
| [Bitrix24](https://docs.qaldy.com/connectors/bitrix24/) | CRM | [[Available]] | Webhook URL | global, Kazakhstan |
| HubSpot | CRM | [[Preview]] | API key | global |
| 1C | Data and docs | [[Planned]] | Username and password | global, Kazakhstan |
| [Airtable](https://docs.qaldy.com/connectors/airtable/) | Data and docs | [[Available]] | API key | global |
| [Google Sheets](https://docs.qaldy.com/connectors/google-sheets/) | Data and docs | [[Preview]] | Service account key file | global, Kazakhstan |
| [Notion](https://docs.qaldy.com/connectors/notion/) | Data and docs | [[Available]] | API key | global |
| [GitHub](https://docs.qaldy.com/connectors/github/) | Developer | [[Preview]] | API key | global |
| [HTTP API](https://docs.qaldy.com/connectors/http/) | Developer | [[Available]] | API key | global |
| [Linear](https://docs.qaldy.com/connectors/linear/) | Developer | [[Preview]] | API key | global |
| [Gmail](https://docs.qaldy.com/connectors/oauth/) | Email | Needs OAuth app | OAuth sign-in | global, Kazakhstan |
| [Postmark](https://docs.qaldy.com/connectors/postmark/) | Email | [[Available]] | API key | global |
| [Resend](https://docs.qaldy.com/connectors/resend/) | Email | [[Available]] | API key | global |
| [Slack](https://docs.qaldy.com/connectors/slack/) | Messaging | [[Available]] | Webhook URL | global |
| [Telegram](https://docs.qaldy.com/connectors/telegram/) | Messaging | [[Available]] | Bot token | global, Kazakhstan |
| [WhatsApp Business](https://docs.qaldy.com/connectors/whatsapp/) | Messaging | [[Preview]] | API key | global, Kazakhstan |

## What the statuses mean

| Status | Meaning |
|---|---|
| [[Available]] | Works end to end through the gate. |
| [[Beta]] | Works, with limits listed on its page. |
| [[Preview]] | Built from the provider's own documentation (an HTTP preset, or the Google Sheets connector tested against a stand-in) and **not yet run against a live account**, so a first call may need a fix. Tell us what the service answered. |
| Needs OAuth app | Waits for an OAuth client to be registered for this install. |
| [[Planned]] | Not served by the gate yet. **It cannot take a key**: the sheet says so and the API refuses one. The HTTP API connector reaches most APIs meanwhile. |

## How a service is reached

- **Native**: Telegram and Google Sheets have their own routes in the gate, with typed actions.
- **A preset on the HTTP API connector**: for a service without a native route, the connection is filled in from a preset: the host, how the key is sent, the narrowest methods and path prefix that do the job, and fixed headers. Presets are ordinary HTTP API connections with the same fence, scrubbing and audit. Resend, Postmark, Slack, Notion, Airtable, Stripe (read-only), GitHub, Linear, WhatsApp Business, Kaspi and Bitrix24 work this way.
- **Any HTTPS API**: the [HTTP API connector](https://docs.qaldy.com/connectors/http/) takes a base URL, an auth style and a key. Only HTTPS on a public host; the admin fixes the host, and the gate pins every call to it.

In every case the app's manifest lists the connector and the actions it uses; anything else is refused.

## Bringing a workflow with you

Already have one in n8n, Zapier or Make? [Import it](https://docs.qaldy.com/connectors/import/): Qaldy reads the export, tells you step by step what maps and what needs a connection, and leaves the result switched off until its owner has reviewed it. [[Preview]]

## How a call flows

```text
app: ctx.connectors.telegram.sendMessage(…)   or   ctx.connectors.http('conn_…').get('/v1/items')
  → https://connector.qaldy.internal/<route>        (resolves nowhere: the sandbox has no network)
  → runtime host signs {app, version, workspace, run, method, url, body hash}
  → gate: verify → is it in the version's manifest? → open the sealed key
          → pin the host, connect only to addresses it checked → call → scrub the key from the reply
  → audit row + City event (a parcel between the app and its gate)
```

## Connect one

1. Open **Connectors** (admins only) and choose the service.
2. The sheet lists the steps, with a **Where to get it** link to the provider's own key page.
3. Paste the key and press **Seal and connect**. It is write-only from now on.
4. Press **Test connection**. The gate makes one harmless call and tells you what the service answered.
5. Build an app that uses it; the plan lists the connector as a sentence for an admin to approve.

The connection belongs to the workspace, not to you. If you leave, it stays. A key can be [replaced without stopping the apps, given an expiry date, and revoked in one step](https://docs.qaldy.com/guides/keys-and-panic/). If a key breaks, the card says **Expired, reconnect** or **Not working, reconnect**, and the apps waiting on it say so too.

## Workspaces that stay in Kazakhstan

A workspace with the strict Kazakhstan policy only allows connectors whose regions include Kazakhstan. An arbitrary HTTP API is global only, because Qaldy cannot vouch for where its data lives. See [Kazakhstan](https://docs.qaldy.com/kazakhstan/).