X (Twitter)

X (Twitter)

The X channel is available in the following applications:

Beesender Chat Master 4.1.3+

Beesender Bot Master 4.1.3+

Creating a Developer account in X

Before starting, make sure you are authorized in X with the account that will be used for integration with the CRM (it will be used to send and receive messages).

Go to the X Developer Console using the link https://console.x.com/

If a developer account has not yet been created, the system will automatically prompt you to register and complete the Developer Agreement & Policy form.

In the opened form:

  • in the Account Name field, specify the integration name, for example:
    Beesender CRM Integration

  • in the Describe all of your use cases of X's data and API field, insert a description of the API usage scenario:

We are integrating X into our CRM system using Beesender Chat / Bot Master to enable customer communication through Direct Messages. The main purpose of this integration is customer support communication. Use cases: - Receive incoming Direct Messages from customers and display them in CRM. - Allow support agents to reply to customers from CRM through the connected X channel. - Store conversation history in CRM for customer support and service quality purposes. - Link X accounts to CRM contacts when the customer communicates with the company through X. We do not use X data for resale, redistribution, advertising, profiling, scraping, or analytics outside of the customer support process. X data is used only to provide customer support communication between the customer and the support team. Access to the data is limited to authorized CRM users.

After filling out the form, select all checkboxes:

  • You understand that you may not resell anything you receive via the X APIs.

  • You accept the Developer Agreement, the Incorporated Developer Terms, and X Developer Policy.

  • You understand your Developer account may be terminated if you violate the Developer Agreement or any of the Incorporated Developer Terms.

Then click Submit.

chrome_UHtNjHcmMa.png

After submitting the form, you need to wait for the developer account to be activated. This usually takes from a few minutes to several hours.

Creating an application (App) in the X Developer Console

After activating the developer account, you need to create an application that will be used to integrate the CRM with X.

  1. Go to the Apps section in the left menu of the Developer Console.

  2. In the Your Apps block, click the Create App button

image-20260427-143424.png
  1. In the opened Create New Client Application window, fill in the fields:

  • Application Name — specify the application name

  • Environment — select Development

  1. After filling in the fields, click Create New Client Application

image-20260427-143452.png

After successfully creating the application, the Application Created Successfully window will appear, displaying the following data:

  • Consumer Key

  • Secret Key

  • Bearer Token

These keys will be used later to configure the X channel on the CRM side.

  1. After saving, click Close

image-20260427-145153.png

These values must be saved immediately (for example, in a text file or secure storage), as they may not be displayed again.

Getting the Access Token and Access Secret

  1. After creating the application, open it and go to the Keys & Tokens tab.

  2. In the OAuth 1.0 Keys section, find the Access Token block and click the Generate button.

o9EurJpIyM.png

After clicking, the following will be generated:

  • Access Token

  • Access Token Secret

image-20260428-081807.png

These values must be saved immediately, as they are used for authorization when the CRM interacts with the X API.

  1. After saving, click Close.

Configuring application permissions (App permissions)

After generating the tokens, you need to configure the application permissions; otherwise, the agent will not be able to send messages from the CRM.

  1. In the application, go to the Keys & Tokens section.

  2. In the User authentication settings block, click the Set up button.

hmMzVYBBP8.png
  1. In the opened form, specify the following parameters:

  • In App permissions, select Read and write and Direct message

chrome_75zQuffJvB.png
  • In Type of App, select Web App, Automated App or Bot

chrome_UPD5b1z8TD.png
  • In the App info section, fill in the required fields:

Callback URI / Redirect URL
Specify any valid URL, for example:

https://balance.beesender.com/

Website URL
Specify the same or any other URL, for example:

https://balance.beesender.com/

The remaining fields (Organization name, Terms of Service, Privacy Policy) can be left empty if they are not required.

  1. After filling in the fields, click Save Changes

image-20260428-084023.png

After changing the application permissions, the previously generated Access Token may still have Read permissions. In this case, you need to go back to the Keys & Tokens section and click Regenerate for the Access Token to obtain a token with updated permissions.

Adding the channel in Creatio

  1. Go to System Designer (settings) → Beesender Chat Configuration → Channels tab.

  2. Click + next to the Channels detail.

  3. Select X.

image-20260428-145904.png
  1. Fill in the field values:

Adding the X channel

Adding the X channel

Channel name

any name of your choice

AccessToken

Access Token (X (Twitter) | Getting the Access Token and Access Secret )

AccessSecret

Access Token Secret (X (Twitter) | Getting the Access Token and Access Secret )

ConsumerKey

Consumer Key (X (Twitter) | Creating an application (App) in the X Developer Console )

ConsumerSecret

Secret Key (X (Twitter) | Creating an application (App) in the X Developer Console )

BearerToken

Bearer Token (X (Twitter) | Creating an application (App) in the X Developer Console )

Chat weight

optional

Channel URL

optional

  1. Click Add

The X channel setup is complete. After saving the channel, assign operators and start working with chats.

If there are no funds or an active plan in the X Developer Platform account:

  • incoming messages from the client will be delivered to the CRM;

  • outgoing messages from the agent will not be sent from the CRM.