woblehelp

Connect X (Twitter)

Agents post, reply, search and read timelines on X with your own developer app; you paste the app's Consumer Key and Secret Key, then authorize on X.

X (Twitter)Sign inProductivity

Post, reply, search and read timelines on X. Direct, with your own API keys.

With X connected, an agent can search public posts from the last 7 days, read a user's recent posts, pull a post's metrics, and, after you approve the exact text, post or reply from the connected account.

Before you start

  • An X account with access to the X developer portal. New developer accounts are billed pay-per-use by X; the portal shows current rates.
  • You must be an owner or admin of the woble workspace.

Connect it

  1. Open Marketplace in the sidebar, switch to the Integrations tab, find X (Twitter) and press Add. Keep the dialog open; it shows the callback URL for step 3.
  2. In the developer portal open your app, or create a project and an app. X shows the API Key and Secret (the Consumer Keys) once; copy both. They can be regenerated under Keys and tokens.
  3. In the app open User authentication settings, press Set up. Choose Read and write under App permissions, Web App, Automated App or Bot under Type of App, paste the callback URL from the dialog, https://<your woble host>/api/oauth/x/callback, into Callback URI / Redirect URL, add a Website URL and save.
  4. In woble, paste the API Key into Consumer Key and the API Key Secret into Secret Key. The Bearer Token is not needed.
  5. Press Authorize on X. A tab opens at x.com; press Authorize app. You return to woble, the card shows Connected with your @username, and the agent panel lists the X tools.

Alternative: generate an Access Token and Secret under Keys and tokens (after setting Read and write) and paste them into the optional fields; the button then says Connect and skips the redirect.

Or ask an agent

Type @ruby connect X in any chat. The same card appears there; only an owner or admin can complete it.

Try it

  • "@atlas what are people saying about #devops this week, excluding retweets?"
  • "@atlas draft a reply to @acme's latest post, show me before posting"

If it does not connect

  • "X refused the callback URL": the callback in User authentication settings does not match the dialog's URL exactly, or user authentication is not set up. Fix it and press Authorize on X again.
  • Posting fails with 403 while reading works: the tokens were made while the app was Read only. Set Read and write, regenerate them, then Remove and reconnect.
  • Wrong account: you were logged into another X account when you authorized. Remove, switch accounts on x.com, reconnect.
  • Test connection in Marketplace, then Connected, checks the keys against your account.

Disconnect

Marketplace, Connected, press Remove next to X. Keys and tokens are deleted and agents lose the X tools immediately.

More in this category

On this page