Get Tweet: X (Twitter) action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Tweet support batch operations?

Yes. Run Get Tweet inside a Loop node to process arrays. Tiny Command handles X (Twitter)'s rate limits automatically so you don't have to throttle manually.

More actions