connect_account
Idempotent
Connect a credential-based social account (telegram, bluesky, discord, wordpress, devto, hashnode, lemmy) directly, without a browser session. Call list_platforms with view=connect_link first to discover the exact credential fields the platform needs. Prefer scoped secrets: app passwords (Bluesky, WordPress), bot tokens (Telegram), webhook URLs (Discord), and API tokens (Dev.to, Hashnode) over primary passwords. Warn the user that any credential they share passes through this conversation. For OAuth platforms (Instagram, X, LinkedIn, ...) use create_connect_session instead.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pat | No | Hashnode: personal access token from Account Settings, Developer. | |
| handle | No | Bluesky: handle, for example posterly.bsky.social. | |
| api_key | No | Dev.to: API key from Settings, Extensions, DEV Community API Keys. | |
| chat_id | No | Telegram: target channel or group chat ID. | |
| instance | No | Lemmy: instance domain, for example lemmy.world. | |
| password | No | Lemmy: account password (TOTP-enabled accounts are not supported). | |
| platform | Yes | Credential-based connection target: telegram, bluesky, discord, wordpress, devto, hashnode, or lemmy. | |
| site_url | No | WordPress: site URL, e.g. https://blog.example.com. | |
| username | No | WordPress: username the application password belongs to. Lemmy: username or email. | |
| bot_token | No | Telegram: bot token from BotFather. | |
| webhook_url | No | Discord: channel webhook URL from channel settings, Integrations, Webhooks. | |
| app_password | No | Bluesky: app password from account settings. WordPress: application password from wp-admin Users, Profile, Application Passwords. | |
| workspace_id | No | Workspace to connect the account into. Workspace-scoped API keys ignore this. | |
| connect_session_id | No | Optional connect session ID to mark connected or failed based on the outcome. |