Run a connector action
Runs one action (`linear.create_issue`) live in the app, on `connectionId` or on the caller's only usable account for that app. Writes on a workspace connection need the `integrations:write` permission; a person's own account (email) is usable only by them and never by an API key. Send an `Idempotency-Key` header to make retries safe; it is also handed to the app where it supports one.
apiKeyAuthorizationBearer <snoze_sk_…>Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
workspaceId*stringapplication/json- body
action*stringinput*connectionId?string|nullSuccess
application/json- response
data*curl -X POST 'https://api.snoze.dev/v1/workspaces/string/connectors/actions/run' \ -H 'Content-Type: application/json' \ -d '{ "action": "string", "input": {}}'{ "data": { "action": "string", "connectionId": "string", "output": null }}List connectors and their actions
Returns every app Snoze can act in (Gmail, Slack, Linear, Stripe, ...) with its actions, each action's input JSON Schema and access level (read, write or destructive), the table columns of actions that read as a table, and the accounts the caller may run each app on in this workspace: the workspace's connections and, for personal apps like email, the caller's own accounts.
Read a connector action as a table
Runs a read action that declares table columns (`stripe.list_invoices`, `linear.search_issues`) and returns its rows keyed by those columns, with when they were read. Nothing is stored: the rows come live from the app, briefly cached. Used by dashboard widgets, page embeds and saving rows to a database.