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.
Create your X project and app
- Go to the X Developer Portal.
- Click Create Project.
- Give the project a name.
- Select Making a bot as the use case.
- Add a project description.
- Create the app and give it a name.
- Copy the generated API Key, API Secret Key, and Bearer Token.
Allow Direct Message permissions
- Open the Settings tab of your X app.
- Under User authentication settings, click Setup.
- Enable OAuth 1.0a.
- Under App permissions, select Read + Write + Direct Messages.
- Add your Callback URI / Redirect URL, Website URL, Terms of service URL, and Privacy policy URL.
- Save the settings.

Generate access credentials
- Open the Keys and tokens tab of your X app.
- In Access Token and Secret, click Generate.
- Copy the Access Token and Access Token Secret.

Apply for the required X API access
- Go to X API products.
- Apply for the required access tier for Direct Messages and Account Activity.
- In the application details, describe that the app will use Direct Messages for customer support.
- Wait for approval from X.
Set up the Account Activity API
- Once approved, go to Dev environments.
- In Account Activity API / Sandbox, click Set up dev environment.
- Give the environment a name.
- Select the app created earlier.

Link X Direct Messages with Crisp
- Go to Crisp.
- Open Plugins → Twitter DM.
- Paste the credentials generated from the X Developer Portal.
- Save the configuration.
Troubleshooting
I do not receive X Direct Messages in Crisp
Check these points first:
- Regenerate and update all X API tokens in the X Developer Portal, then save the new values in Crisp.
- Make sure OAuth permissions are set to Read + Write + Direct Messages.
- Confirm the Account Activity API dev environment is properly configured.
- In X message settings, make sure message requests are allowed and Filter low-quality messages is disabled if it blocks expected messages.
Updated on: 03/05/2026
Thank you!