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 catalog#

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

What the statuses mean#

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 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: 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#

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