---
title: X (formerly Twitter)
slug: x-formerly-twitter
docTags:
createdAt: 2022-05-11T08:35:06.000Z
---
## 1. Introduction
X (formerly known as Twitter) is an online social networking and microblogging service where users post and interact with messages known as “posts” (previously “tweets”). If you're looking to deploy your chatbot on X, Engati enables seamless integration.
Any user who sends a direct message (DM) to your X account will experience the conversational flow you’ve designed for your bot. The bot will also handle any FAQs it has been trained to answer.
🔹 **Note:** Once you start interacting with users via X, their messages will appear in the **Messages** tab in your Engati inbox, just like WhatsApp and Instagram conversations.
### 1.1 Access to Setup
1\. To configure X as a deployment channel:
Go to **Configure > Deployments > X (Twitter)**
## 2. Requirements
To link your bot with your X account:
- You need a **developer account** on X, created using the same email as your X account.
- Visit [https://apps.twitter.com/](https://apps.twitter.com/) to create your developer account.
- X will verify your use case for the API — this process typically takes 2–3 business days.
- Once verified, you can proceed with the app setup.
## 3. Steps to configure Twitter as a Channel
Here’s how you deploy your chatbot on Twitter
### 3.1 Create an app
- Log into your X [Developer Portal](https://developer.twitter.com/) and create an application.
- Go to **Projects & Apps → Overview**
- Under “Standalone Apps,” click on **Create App** and set your app name.
Setup the app name.
You can copy the API Key and API secret key. Click on App Settings
### 3.2 Set appropriate permissions
- In **App Settings**, click **Edit** near **App Permissions**.
- Choose **Read, Write, and Access Direct Messages**, then **Save**.
- This is required for your chatbot to handle conversations.
### 3.3 Retrieve the required tokens and keys
Go to the **Keys and Tokens** section and collect the following:
- API Key (Consumer Key)
- API Secret Key (Consumer Secret)
- Access Token
- Access Token Secret
You'll need these in Step 3.7 while setting up on Engati.
### 3.4 Get account activity API access
- Apply for either **Premium** or **Enterprise** access via the [Account Activity API documentation](https://developer.twitter.com/en/docs/twitter-api/enterprise/account-activity-api/overview).
- This access type must be correctly selected on the Engati portal during setup.
::Image[]{src="https://api.archbee.com/api/optimize/FEqjvWZnyymr_PEhXLLlG/o73-V6ramjvdbgoZBHe2o_image.png" size="50" width="571" height="615" position="center" showCaption="false"}
### 3.5 Set up developer environment
- Go to the Dev [Environments](https://developer.twitter.com/en/account/environments) section.
- Click **Set up dev environment** for **Account Activity API**.
- Assign an environment name and link your Twitter app ID.
- This name becomes your **Dev Environment Label**, which you’ll use in Step 3.7.
### 3.6 Allow receiving direct messages
For your account, go to the [Security](https://twitter.com/settings/safety) section and check the “Receive Direct Messages from anyone” from the bottom of the page and then save the changes.
### 3.7 Update details on Engati portal
Update the following details in the Twitter configuration section under Deploy->Twitter and click on the save button your bot is ready to respond to all your direct messages on Twitter.
– Twitter Admin username(the name for your Twitter Handle)
– Consumer Key(from Step 3)
– Consumer Secret(from Step 3)
– Access Token(from Step 3)
– Access Token Secret(from Step 3)
– Dev Environment Label(from Step 5)
– The appropriate Twitter Account type, namely – Premium or Enterprise. (based on the account type)
::Image[]{src="https://api.archbee.com/api/optimize/FEqjvWZnyymr_PEhXLLlG/TMwIMsAlhWKU1LofhapaS_image.png" size="74" width="577" height="662" position="center" showCaption="false"}