Tools

connections_create_with_credentials

Connect a social account that has NO browser consent screen — today that is Bluesky, which authorizes with a handle plus an app password.

Connect a social account that has NO browser consent screen — today that is Bluesky, which authorizes with a handle plus an app password. Read connect_method and credential_fields from capabilities first: a provider with connect_method “oauth” must use connections_create instead, and this call will refuse it. Unlike connections_create there is nothing to poll — the grant exists when this returns, so go straight to connections_destinations with the returned integration_id. Ask the HUMAN for the credential values; never invent them, and never reuse an account password where an app password is asked for.

Input

FieldTypeRequiredDescription
organizationstringnoOrganization slug to act in (see organizations_list). Optional: API keys are bound to one organization; OAuth connections default to your active organization.
provider"fake" | "linkedin" | "mastodon" | "x" | "instagram" | "facebook" | "threads" | "bluesky" | "tiktok" | "youtube"yesProvider to connect
credentialsobjectyesValues for the provider’s own credential_fields, keyed by field name. Secrets in transit only — they are traded for tokens and never stored.

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 connectionsCreateWithCredentials run the same guarded procedure the dashboard uses — same permissions, same validation, same tenant isolation.