Connect an integration
Starts a connection to an integration. For OAuth providers it returns a URL to send the user to for authorization. For API-key providers, send the credentials in the request body; they are stored securely and never returned. Returns an error if the provider is not yet available to connect.
Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.
Path Parameters
google_calendar, google_sheets, calendly, hubspot, square, opentable, shopify, postgres, mysql Body
Optional connect body. For an api_key provider supply credentials (ignored for oauth2). The required credential KEYS depend on the provider kind: • Most api_key providers: { "apiKey": "..." }. • SQL databases (postgres, mysql): a structured connection descriptor — host (required), port (required, string), database (required), user (required), password (required), sslmode (required; one of require | verify-ca | verify-full — disable is refused at the connect boundary), and ca_pem (optional PEM for verify-ca/ verify-full). Prefer a least-privilege read-only role (see GET /integrations/{kind}/sql/scripts), and validate first with POST /integrations/{kind}/sql/test.
{
"host": "db.example.com",
"port": "5432",
"database": "appdb",
"user": "flowyte_readonly",
"password": "<secret>",
"sslmode": "verify-full"
}