Twitter (X)

Post tweets, search, manage users and followers via the Twitter/X API v2.

Detail	Value
Category	Social Media
Base URL	https://api.twitter.com/2
Authentication	OAuth2
Endpoints	6
Connector key	twitter

Using Twitter (X) in a workflow

1. Go to Connections and click New Connection.
2. Pick Twitter (X) from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
POST /tweets	Create a tweet
GET /tweets/{tweetId}	Get a tweet
GET /tweets/search/recent	Search recent tweets
GET /users/me	Get authenticated user
GET /users/{userId}/tweets	Get user tweets
GET /users/{userId}/followers	Get followers

Each endpoint is documented in full below. Use the outline on the right to jump to one.

POST /tweets

Create a tweet

Detail	Value
Operation ID	social.createTweet
Method	POST
Path	/tweets

Parameters

No parameters.

Request Body

Field	Type
text	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Twitter (X) connection from the Connection dropdown.
3. In the Operation dropdown, select social.createTweet.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Twitter (X) API reference.

GET /tweets/{tweetId}

Get a tweet

Detail	Value
Operation ID	social.getTweet
Method	GET
Path	/tweets/{tweetId}

Parameters

Name	Location	Type	Required
tweetId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Twitter (X) connection from the Connection dropdown.
3. In the Operation dropdown, select social.getTweet.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Twitter (X) API reference.

GET /tweets/search/recent

Search recent tweets

Detail	Value
Operation ID	social.searchTweets
Method	GET
Path	/tweets/search/recent

Parameters

Name	Location	Type	Required
query	query	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Twitter (X) connection from the Connection dropdown.
3. In the Operation dropdown, select social.searchTweets.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Twitter (X) API reference.

GET /users/me

Get authenticated user

Detail	Value
Operation ID	social.getMe
Method	GET
Path	/users/me

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Twitter (X) connection from the Connection dropdown.
3. In the Operation dropdown, select social.getMe.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Twitter (X) API reference.

GET /users/{userId}/tweets

Get user tweets

Detail	Value
Operation ID	social.getUserTweets
Method	GET
Path	/users/{userId}/tweets

Parameters

Name	Location	Type	Required
userId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Twitter (X) connection from the Connection dropdown.
3. In the Operation dropdown, select social.getUserTweets.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Twitter (X) API reference.

GET /users/{userId}/followers

Get followers

Detail	Value
Operation ID	social.getFollowers
Method	GET
Path	/users/{userId}/followers

Parameters

Name	Location	Type	Required
userId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Twitter (X) connection from the Connection dropdown.
3. In the Operation dropdown, select social.getFollowers.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Twitter (X) API reference.