Skip to main content
X lets the assistant answer when someone mentions the connected account in a post, or sends it a direct message. The reply stays on X, and the thread is kept in History. Pictures and files on this channel are not received as media.

​
When to use it

Use it for a public support handle or a direct-message inbox on X. Connecting an assistant means those mentions and direct messages are answered with that assistant’s instructions and tools, instead of waiting in the X inbox.

​
What the assistant hears

The assistant hears post mentions and direct messages for the account that authorized the app. X checks the webhook with a CRC challenge, and Famulor answers that check. Subscribe to post.mention.create, dm.received and dm.sent.

​
Where the keys come from

The linked provider guide shows the screens for these clicks. Follow the clicks below together with those pictures. Create a project and an app at developer.x.com. Under Keys and tokens, copy the API Key Secret. That is the API Key Secret (consumer secret) on the Famulor card. Also turn on OAuth 2.0 user authentication with the scopes tweet.read, tweet.write, users.read, dm.read, dm.write, like.write and offline.access. Complete the sign-in for the bot account and keep either the user access token, or the client ID together with the refresh token. The webhook itself is registered in the X developer console. Official guide: Activity API.

​
Create it at the provider

  1. At developer.x.com, create a project and an app.
  2. Open Keys and tokens and copy the API Key Secret.
  3. Enable OAuth 2.0 for the bot user with the scopes listed above.
  4. Finish the sign-in and copy the user access token, or the client ID and the refresh token.
  5. Optional: copy the bot user ID and the @handle if you already have them. Famulor can store both on the card.

​
Connect it in Famulor

Your plan includes this channel. Open Settings → Channels, choose the card, name the connection, pick an assistant and save. The shared conversation settings — response delay (default 5 seconds) and inactivity timeout (default 30 minutes) — are described on the messaging channels page. On the X card, API Key Secret (consumer secret) is required. Also paste either OAuth 2.0 user access token, or both OAuth client ID (optional, managed refresh) and OAuth refresh token (optional). Bot user ID (optional) and Bot @handle (optional) can stay empty.

​
Point the provider at Famulor

  1. Copy the Famulor webhook URL from the connection menu. It must be public HTTPS with no port in the address.
  2. In the X developer console, register that URL as the Activity API webhook. X sends a CRC challenge, and Famulor answers it.
  3. Subscribe to post.mention.create, dm.received and dm.sent. The bot account has to have authorized the app first.
  4. A new mention or direct message appears in History.

​
History

Open History and filter by X. The thread, the assistant reply and any analysis appear there. You can pause the assistant and answer manually.

​
API, MCP and command line

Create this connection in the dashboard. The public API and the command line cannot pass every value this card asks for, so they cannot finish this setup. The card needs the API Key Secret, and a public create call does not accept that value.