Connect X and private messaging

Authorize the intended account

1. Open Config and select Connect X.
2. Review the account and authorization requested in the X sign-in flow.
3. Return to CookMyBots and confirm the connected username.
4. Complete any additional setup shown for the features your bot needs, then publish a validated version.
5. Test an authorized mention or other intended interaction and inspect current platform status.

X connects through OAuth. You do not paste an X password into CookMyBots. Available mentions, replies, searches, posting, metrics, and private messaging depend on the authorization and API access available to the connected account. Read feature-specific setup rather than assuming all access arrived together.

Use X features from another bot

A Telegram or WhatsApp bot can use CookMyBots’ X integration even when people interact with it on another platform. Connect your X account to that same project when its features need X access. Connecting Telegram or pairing WhatsApp does not authorize X.

For example, a Telegram bot that summarises X profiles needs its Telegram connection to receive messages and its X connection to fetch the requested X data. Its customers can continue using Telegram.

1. Describe the X feature in your build request, or ask BOTS SI to add it to your existing bot.
2. When the X integration is part of the project, open Config and expand Connect X Account.
3. Select Connect X, authorize the intended account, and return to confirm its username.
4. Connect the bot’s main platform separately using its Telegram connection or WhatsApp pairing flow.
5. Keep sufficient wallet credits for billable X API requests, hosting, and any AI the feature uses.
6. Follow the current publishing action for saved changes, then test the X feature from the platform your customers use.

If Connect X is missing, ask BOTS SI to review or add the required X integration. A linked X account still needs the permissions and API access required by the feature; it does not guarantee every X action is available.

Build a bot that serves customers on several platforms

Set up private conversations separately

Encrypted XChat needs separate authorization in Config. Use a dedicated bot account: approval allows access to its past and future encrypted conversations and replies, and messages used for AI answers may be processed by the AI service. Review that consent before continuing.

Complete existing encrypted-chat setup in X first, then use your existing PIN in the dedicated setup field. CookMyBots cannot create or reset it. The PIN stays on your device. Regular unencrypted DMs do not need this key setup. Once keys are secured, check delivery status instead of repeatedly entering the PIN.

Test private delivery from another eligible account. A support bot must never post private ticket details or conversations publicly when delivery fails.

Allow for API usage and backoff

Billable X API reads and writes are charged from your CookMyBots wallet, separately from AI replies and hosting. An X request can incur a charge without using AI. Authorizing an X account does not fund its usage. New paid requests need sufficient available credits.

Requests may be limited, delayed, or backed off; check health and Billing before reconnecting. Publishing workflows should include owner approval, cancellation, duplicate prevention, and honest failure states.

Billing includes recorded X usage details and an endpoint rate directory. The directory shows configured base rates before service fees, not a guaranteed final quote or a live X account balance. Use the recorded charge details to understand completed usage.

Disconnect X and review account authorization

Disconnect in Config removes this project’s saved X connection and message subscriptions. It does not remove CookMyBots from X Connected Apps. To withdraw that authorization too, review Connected Apps in X and remove the relevant access. Reauthorize the intended account before using X features again.

Understand connection cleanup when permanently deleting a project