Skip to main content
Connecting a network happens in the browser. You never send your API key to Facebook, LinkedIn, or X. Connect hosts OAuth, Page pickers, and the credential screens (Bluesky app password, Mastodon instance, Telegram /connect code). There is no MCP connect tool. An agent publishes to accounts that are already connected. For yourself, connect from Accounts in the dashboard. For your users, start the same flow from your backend and send them to the URL Connect returns. Paths and query params: Connect social account.

​
What the user sees

You do not send people to the Connect dashboard to finish this.

​
When they come back

On success, the browser lands on the return URL you passed in, with the network and the new social-account id. On failure, the same URL gets an error instead. Read identities by id, not by network name. The same network can appear more than once (two LinkedIns, three Instagrams). The same person cannot sit twice — reconnecting updates the existing row. Instagram Login and Instagram via Facebook are one identity, not two. A connected account can later show as expired. Connect skips expired identities at publish time until the user reconnects.

​
After they are connected

  • Group them with social sets.
  • Disconnect from the dashboard or the API.
  • Pinterest needs a board and Discord needs a channel before you can publish — pick those when you compose the post.
Connecting X, or a third non-X identity, without a card is refused.