ActionX (Twitter)Updated September 2026

How do I fetch a tweet by ID on X/Twitter?

Short answer: You can get tweet in X (Twitter) by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the X (Twitter) Get Tweet action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Tweet in X (Twitter) — start free All 10 X (Twitter) actions

Get Tweet in X (Twitter) — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Tweet ID tweet_id	string	Required	The ID of the tweet to retrieve

Sample request

{
  "tweet_id": "{{trigger.tweet_id}}"
}

Returns

{
  "data": {
    "id": "1234567890",
    "text": "Hello world!",
    "author_id": "456",
    "created_at": "2026-04-20T10:00:00Z",
    "public_metrics": {
      "like_count": 10,
      "quote_count": 1,
      "reply_count": 2,
      "retweet_count": 5
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Tweet.

Any of these apps can fire this action as part of a workflow.

Google Sheets → X (Twitter)

2 Google Sheets triggers

HubSpot → X (Twitter)

18 HubSpot triggers

FAQ

Questions about Get Tweet.

What does the Get Tweet action do in X (Twitter)?

Gets a single tweet by its ID with full details (text, author, timestamps, public metrics, attachments). The standard read after a trigger fires with an ID.

What inputs does Get Tweet require?

Required: Tweet ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if X (Twitter) returns an error?

The run history shows the failed step with its input and the error message X (Twitter) returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Tweet support batch operations?

Run Get Tweet inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within X (Twitter)'s rate limits.

More actions