Connect your X account
Configure the developer app, authorize the right account and test access.
On this page
Before you begin
Your own X developer app and suitable API access. Your administrator must configure a base64-encoded 32-byte X_CREDENTIAL_KEY on the server.
Steps
Check the active account in the workspace's account switcher. In your X developer app, enable OAuth 2.0 user authentication and configure the app type/permissions needed for that account's publishing workflow.
Open Settings → Connections → X publishing and choose Add developer app details, or Edit developer app details for a saved connection. Copy the exact callback URL shown in that editor: your workspace origin followed by /api/x/callback. Register it in the developer app.
Enter the developer app's client ID and, when required for its app type, client secret in the same editor. Save those app details.
Choose Connect X. Sign in to X and authorize the intended account, then return to the workspace.
Check the displayed username, account ID and granted scopes. Choose Test connection.
Under Post publishing, choose Edit publishing settings. Enable Publish through X when you want approved API delivery, leave Pause automation off to allow delivery, then choose Save automation settings. Each post still needs your explicit approval.
A practical example
If you have Personal and Studio profiles, switch to Studio before connecting its X account. Verify the returned @username in Settings before approving a Studio post.
Check the result
The workspace identifies the intended X account and reports the connection test result.
Troubleshooting
A callback mismatch must be corrected on both sides. Missing server encryption configuration needs your administrator. API access or scope errors must be resolved in your X developer account; reconnect after changing authorization.