Tools
connections_destinations
After a connection completes: the publishable destinations (profile, pages) the new grant can post to, with `connected` marking ones already present.
After a connection completes: the publishable destinations (profile, pages) the new grant can post to, with connected marking ones already present. Pick with connections_select — no channel exists until then.
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. |
connect_id | string | yes | A COMPLETED connection id |
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 connectionsDestinations run the same guarded procedure the dashboard uses — same permissions, same validation, same tenant isolation.