SnozeDevelopers
API referenceConnected Accounts

Rebind an automation's credential

Changes which credential an automation runs on, or clears the pin so its nodes fall back to their workspace connection. Deliberately separate from saving the graph: editing conditions or mappings must never silently remove the only credential that works. The current run-as owner may swap the pin for another of their own accounts without further permission; clearing it, moving it onto a workspace connection, or any change by someone else needs `automations:write`. A personal credential can only ever be bound by the person who owns it, and is rejected outright when the workspace requires workspace connections. A workspace target may be a connection created through the connections API or an enabled provider install.

PUT
/v1/workspaces/{workspaceId}/automations/{automationId}/run-as

Authorization

apiKey
headerAuthorizationBearer <snoze_sk_…>

Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.

Path Parameters

workspaceId*string
automationId*string

Request Body

application/json
  1. body
runAs*||null

Response Body

Success

application/json
  1. response
data*
Example Request
curl -X PUT 'https://api.snoze.dev/v1/workspaces/string/automations/string/run-as' \  -H 'Content-Type: application/json' \  -d '{  "runAs": {    "kind": "workspace",    "connectionId": "string"  }}'
Example Response
{  "data": {    "automationId": "string",    "runAs": null  }}

Resolve shared resources for this viewer

Answers, for the signed-in viewer only, whether each referenced external resource is reachable through one of their own credentials. Never resolves through the credential of whoever placed the reference. At most 50 distinct refs per request (the payload accepts up to 400 ids before de-duplication); more is a validation error, not a truncated answer. Answers are cached per viewer and per satisfying account, positively for ten minutes and negatively for two so newly granted access appears quickly; `forceRecheck` clears the cached answers first. A probe that errors or exceeds five seconds renders as no access rather than falling back to another credential. A redacted ref the viewer cannot reach carries no name, URL or provider id.

Read this workspace's connection policy

Returns whether personal accounts are blocked in this workspace and whether unattended automations must run on a workspace connection. Both default to off, so a workspace that has never opened the setting reports a permissive policy. Requires `integrations:read`.