Enterprise Tool

Twitter / X

Post tweets, search, reply, and monitor timelines via the Twitter/X API v2

Twitter/X API v2 lets you post, reply, delete, and like tweets, as well as read user timelines and search recent tweets. Twitter uses two separate auth systems: a single Bearer Token for reading public data, and four OAuth 1.0a credentials for writing (posting, liking, deleting). You only need the credentials for the operations you actually use — Bearer Token alone is enough for search/read workflows, and the four OAuth keys alone are enough for posting. Because Twitter does not offer traditional webhooks, monitoring workflows (e.g. watching for mentions) should use a cron schedule combined with the search_tweets or get_timeline operation.

Official documentation

Setup

Create a Twitter Developer App

Go to developer.twitter.com and sign in. Create a Project and an App inside it. Under the App settings, set the App permissions to 'Read and Write' (required for posting tweets). Note: Free tier allows 500 posts/month.

Twitter Developer Portal

Get your Bearer Token

In the App dashboard go to Keys and Tokens > Bearer Token. Copy it. The Bearer Token is used for all read operations (get_tweet, get_user, get_timeline, search_tweets).

Get your OAuth 1.0a credentials

In Keys and Tokens, copy your API Key (Consumer Key) and API Key Secret. Then under Authentication Tokens, generate an Access Token and Access Token Secret. These are required for write operations (post_tweet, reply_tweet, delete_tweet, like_tweet).

Add the integration in CipherSense Agents

Go to Project > Integrations > Add Integration > Twitter / X. Enter your Bearer Token and, if you need write access, all four OAuth 1.0a keys. Click Save & Test.

Connection Fields

Fields required when adding this integration in your Project › Integrations.

Field	Required	Description
Bearer Token	Optional	Needed for READ operations (get_tweet, get_user, search_tweets, get_timeline). This is a single app-level token — copy it from Developer Portal > App > Keys and Tokens. If you only need to read data, this is the only credential you need.
API Key	Optional	Needed for WRITE operations (post_tweet, reply_tweet, delete_tweet, like_tweet). This identifies your Twitter App — like a username for your app. Found in Developer Portal > App > Keys and Tokens.
API Key Secret	Optional	Needed for WRITE operations. This is the password for your app identity. Keep it secret. Found alongside the API Key.
Access Token	Optional	Needed for WRITE operations. This represents YOUR Twitter account's permission to let the app act on its behalf (post, like, delete). Generate it in Developer Portal > App > Keys and Tokens > Authentication Tokens.
Access Token Secret	Optional	Needed for WRITE operations. The secret paired with your Access Token — together they prove your account has authorised the app. Generated alongside the Access Token.

Common Use Cases

Post AI-generated content summaries or announcements automaticallyMonitor competitor mentions with cron + search_tweets → AI analysis → Slack alertAuto-reply to mentions: poll timeline → filter keywords → AI drafts reply → postThread creation: AI generates long content → split into 280-char chunks → post as repliesSocial listening: track a keyword daily, summarise sentiment with AI, email reportHuman-in-the-loop: AI drafts tweet → HITL approval node → post on approval

Ready to connect Twitter / X?

Add this integration from your project dashboard and wire it into a workflow.

Open Dashboard ← Back to Integrations