# Twitter AI integration on Definable

> Twitter, Inc.

## What this connects

Twitter, Inc. was an American social media company based in San Francisco, California, which operated and was named for named for its flagship social media network prior to its rebrand as X.

Vendor: https://x.com

## Tools available

**79** tools available. First 12:

- `TWITTER_ADD_LIST_MEMBER` — Add a list member — Adds a user to a specified Twitter List; the list must be owned by the authenticated user.
- `TWITTER_ADD_POST_TO_BOOKMARKS` — Add post to bookmarks — Adds a specified, existing, and accessible Tweet to a user's bookmarks, with success indicated by the 'bookmarked' field in the response.
- `TWITTER_APPEND_MEDIA_UPLOAD` — Append Media Upload — Append data chunk to an ongoing media upload session on X/Twitter. Use this action during chunked media uploads to append each segment of media data in sequence.
- `TWITTER_BOOKMARKS_BY_USER` — Get bookmarks by user — Retrieves Tweets bookmarked by the authenticated user, where the provided User ID must match the authenticated user's ID.
- `TWITTER_CREATE_ACTIVITY_SUBSCRIPTION` — Create activity subscription — Tool to create a subscription for an X activity event. Use when you need to monitor specific user activities like profile updates, follows, or spaces events.
- `TWITTER_CREATE_COMPLIANCE_JOB` — Create compliance job — Creates a new compliance job to check the status of Tweet or user IDs; upload IDs as a plain text file (one ID per line) to the `upload_url` received in the response.
- `TWITTER_CREATE_DM_CONVERSATION` — Create group DM conversation — Creates a new group Direct Message (DM) conversation on Twitter. REQUIRED PARAMETERS: - conversation_type: Must be 'Group' - participant_ids: List of Twitter user IDs to include in the conversation - message: JSON object with the initial message. Must contain 'text' field. To include media attachments, use message.attachments array with media_id (NOT media_url): {"text": "...", "attachments": [{"media_id": "1234567890"}]} Note: Media must be uploaded first using the upload_media action to obtain a media_id.
- `TWITTER_CREATE_LIST` — Create a list — Creates a new, empty List on X (formerly Twitter), for which the provided name must be unique for the authenticated user; accounts are added separately.
- `TWITTER_CREATION_OF_A_POST` — Create a post — Creates a Tweet on Twitter; `text` is required unless `card_uri`, `media_media_ids`, `poll_options`, or `quote_tweet_id` is provided. Example - Creating a tweet with media and location: { "text": "Check out our latest product update! 🚀", "media_media_ids": ["1455952740635586573"], "geo_place_id": "df51dec6f4ee2b2c" } Example - Quote tweet with commentary: { "text": "This is a game-changer for the industry! Here's why... 🧵", "quote_tweet_id": "1453828617121234945" } Example - Reply to a tweet: { "text": "Great point! Here's my take on this...", "reply_in_reply_to_tweet_id": "1453828617121234945" }
- `TWITTER_DELETE_DM` — Delete direct message — Permanently deletes a specific Twitter Direct Message (DM) event using its `event_id` if the authenticated user sent it; this action is irreversible and does not delete entire conversations.
- `TWITTER_DELETE_LIST` — Delete list — Permanently deletes a specified Twitter List using its ID, which must be owned by the authenticated user; this action is irreversible and the list must already exist.
- `TWITTER_FOLLOWERS_BY_USER_ID` — Get followers by user id — Retrieves a list of users who follow a specified public Twitter user ID.

## Auth

Auth schemes: `OAUTH2`.

## How agents use Twitter

Inside a Definable workflow, Twitter is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Twitter** — the Researcher (GPT-5.5) pulls context from Twitter (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Twitter** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Twitter (create record, post message, draft email).
- **Designer / Engineer → Distributor → Twitter** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Twitter (attach file, open PR comment, post status).

The Verifier checks every Twitter call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- social media accounts — https://definable.ai/apps/category/social-media-accounts/
- social media marketing — https://definable.ai/apps/category/social-media-marketing/

## Related

- HTML page: https://definable.ai/apps/twitter/
- Same category (social media accounts): https://definable.ai/apps/category/social-media-accounts/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt