> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.crisp.chat/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to connect Twitter (X) with Crisp

*Learn how to connect X (Twitter) Direct Messages to Crisp so your team can receive and reply to DMs from the Inbox.*

The **X (Twitter)** integration connects Direct Messages to Crisp. It requires the right X developer access and app permissions, so most setup work happens in the X Developer Portal before the credentials are added to Crisp.

| The X (Twitter) integration is available from the **Crisp Mini** plan.

||| This integration requires the **X/Twitter Enterprise** plan. Without the required X developer access, the integration will not work.

---

# ${color}[#0080dd](Create your X project and app)

1. Go to the [**X Developer Portal**](https://developer.twitter.com/en/portal/dashboard).
2. Click **Create Project**.
3. Give the project a name.
4. Select **Making a bot** as the use case.
5. Add a project description.
6. Create the app and give it a name.
7. Copy the generated **API Key**, **API Secret Key**, and **Bearer Token**.

---

# ${color}[#0080dd](Allow Direct Message permissions)

1. Open the **Settings** tab of your X app.
2. Under **User authentication settings**, click **Setup**.
3. Enable **OAuth 1.0a**.
4. Under **App permissions**, select **Read + Write + Direct Messages**.
5. Add your **Callback URI / Redirect URL**, **Website URL**, **Terms of service URL**, and **Privacy policy URL**.
6. Save the settings.

![X app permissions for Direct Messages](https://storage.crisp.chat/users/helpdesk/website/754190078c1a2c00/image_1npmjgm.png =1000xauto)

---

# ${color}[#0080dd](Generate access credentials)

1. Open the **Keys and tokens** tab of your X app.
2. In **Access Token and Secret**, click **Generate**.
3. Copy the **Access Token** and **Access Token Secret**.

![Generate X access token and secret](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/twitter-access_w9opt.png =1000xauto)

---

# ${color}[#0080dd](Apply for the required X API access)

1. Go to [**X API products**](https://developer.twitter.com/en/portal/products).
2. Apply for the required access tier for Direct Messages and Account Activity.
3. In the application details, describe that the app will use Direct Messages for customer support.
4. Wait for approval from X.

|| The X Developer Portal can change labels and plan names over time. Follow the current X interface while making sure your app has Direct Message and Account Activity access.

---

# ${color}[#0080dd](Set up the Account Activity API)

1. Once approved, go to [**Dev environments**](https://developer.twitter.com/en/account/environments).
2. In **Account Activity API / Sandbox**, click **Set up dev environment**.
3. Give the environment a name.
4. Select the app created earlier.

![Set up the X Account Activity API](https://storage.crisp.chat/users/helpdesk/website/754190078c1a2c00/image_1rankn0.png =1000xauto)

---

# ${color}[#0080dd](Link X Direct Messages with Crisp)

1. Go to [**Crisp**](https://app.crisp.chat).
2. Open **Plugins → Twitter DM**.
3. Paste the credentials generated from the X Developer Portal.
4. Save the configuration.

|| The video below was recorded before changes to the X Developer Portal. The general setup remains similar, but the current interface may use different labels.

${youtube}[Setup Guide](jLl6ZlaE14I)

---

# ${color}[#0080dd](Troubleshooting)

###### ${color}[#F08820](I do not receive X Direct Messages in Crisp)

Check these points first:

1. Regenerate and update all X API tokens in the X Developer Portal, then save the new values in Crisp.
2. Make sure OAuth permissions are set to **Read + Write + Direct Messages**.
3. Confirm the **Account Activity API** dev environment is properly configured.
4. In X message settings, make sure message requests are allowed and **Filter low-quality messages** is disabled if it blocks expected messages.

| Learn more about centralizing social messaging from the [Crisp social inbox page](https://crisp.chat/en/shared-inbox/social-messaging/).