ActionX (Twitter)Updated September 2026

How do I post a tweet on X from a workflow?

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

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

Post 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 Text text	textarea	Required	The text content of the tweet (max 280 characters)
Reply To Tweet ID in_reply_to_tweet_id	string	Optional	Tweet ID to reply to. Makes this tweet a reply.
Quote Tweet ID quote_tweet_id	string	Optional	Tweet ID to quote. Makes this a quote tweet.

Sample request

{
  "text": "{{trigger.text}}",
  "in_reply_to_tweet_id": "{{trigger.in_reply_to_tweet_id}}",
  "quote_tweet_id": "{{trigger.quote_tweet_id}}"
}

Returns

{
  "data": {
    "id": "1234567890",
    "text": "Hello world!"
  }
}

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

Triggered by

Apps that pair well as the trigger for Post 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 Post Tweet.

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

Posts a new tweet to X/Twitter with up to 280 characters (more for X Premium). Supports reply, quote-tweet, polls, and media. Free API tier is heavily rate-limited.

What inputs does Post Tweet require?

Required: Tweet Text. 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 Post Tweet support batch operations?

Run Post 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