channels_disconnect
Disconnect one channel: it stops accepting posts and disappears from pickers; scheduled posts targeting it return to draft.
Disconnect one channel: it stops accepting posts and disappears from pickers; scheduled posts targeting it return to draft. History survives, and re-picking the same destination later reconnects it in place.
Input
| Field | Type | Required | Description |
|---|---|---|---|
organization | string | no | Organization slug to act in (see organizations_list). Optional: API keys are bound to one organization; OAuth connections default to your active organization. |
channel_id | string | yes | Channel id to disconnect |
Result
JSON on success. A refusal comes back as an error prefixed with its code (NOT_FOUND, FORBIDDEN, TOO_MANY_REQUESTS, …) and a message written to be acted on — read it before retrying.
The same operation elsewhere
This tool and the REST operation channelsDisconnect and the CLI command inklate channels disconnect run the same guarded procedure the dashboard uses — same permissions, same validation, same tenant isolation.
channels_creator_policy
What THIS creator's account currently allows on a channel, read live from the provider: the privacy levels they may post as, the interactions their account has LOCKED off, and their own maximum clip length.
capabilities
What each connected channel can do RIGHT NOW (publish verdict with the reason when blocked — missing scope, disconnected, unsupported), plus every provider's platform manifest (text limits, metrics, platform_options sch…