Skip to content
cantila

Connections

Account-wide integrations and credentials. Connect Gmail, Slack, Notion, Stripe, or OpenAI once, then reuse the connection by id across workflows. The credential stays in Cantila's secrets manager and is injected just-in-time at run time — never copied into a workflow definition.

Connections — phase 2

What works today

  • Live today: API-key and basic-auth providers, plus list + create. You can store a credential and reference it by id.
  • Pending: OAuth start/callback flows and the ~15-provider catalog land later in Phase 2.

Creating a connection

curl -X POST https://api.cantila.app/v1/connections \
  -H "Authorization: Bearer $CANTILA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "openai",
    "name": "prod-openai",
    "auth": { "type": "api_key", "key": "sk-..." }
  }'
# List connections
curl https://api.cantila.app/v1/connections \
  -H "Authorization: Bearer $CANTILA_API_KEY"

How credentials are used

A connection is referenced by id from an Automation step. At run time Cantila pulls the secret from its secrets manager and injects it just-in-time into the running step — the credential is never stored in the workflow itself.

API reference

MethodPathStatusNotes
GET/v1/connectionsLiveList connections
POST/v1/connectionsLiveCreate (API-key / basic today)
*/v1/connections/*Phase 2OAuth start/callback + catalog

OAuth-based providers (which need the start/callback dance) and the broader provider catalog are Phase 2. Today, providers that authenticate with an API key or basic credentials are fully usable.