What breaks if I disconnect this account
Lists the automations pinned to this credential that will pause, and how many shared resources the caller will stop being able to reach, so a disconnect names its consequences before it happens.
apiKeyAuthorizationBearer <snoze_sk_…>Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
accountId*stringSuccess
application/json- response
data*curl -X GET 'https://api.snoze.dev/v1/me/connected-accounts/string/deletion-preview'{ "data": { "pausedAutomations": [ { "id": "string", "label": "string", "workspaceId": "string" } ], "affectedRefs": 0 }}Activate or deactivate one of my accounts here
Turns the caller's own connected account on or off for this workspace. Only the owner may change their own grant, and only in a workspace they belong to. `sharedWithWorkspace` is independent of `enabled`: omitting it leaves sharing as it is, `true` additionally requires `integrations:write` and is rejected for credentials the provider did not hand over as an org-owned installation. Turning a grant off, or un-sharing it, immediately drops every cached reachability answer that resolved through it, so shared surfaces stop rendering on the next read rather than at the next cache expiry.
Disconnect an account
Removes the caller's account-level credential and every grant, cached reachability answer, and stored secret that belonged to it. The workspace install the credential was mirrored from is disabled and stripped of its copy of the token, and its Google push channels are stopped, so Snoze stops syncing and receiving data for the account immediately. Automations pinned to it are paused rather than silently re-run under a different identity.