Short answer: Drop the "Twitter / X → Post Tweet" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Tweet Text text | string | Required | Max 280 characters |
Reply To Tweet ID reply_to | string | Optional | Make this tweet a reply to another tweet |
{"text": "e.g. Just shipped v2.0! Check it out at...","reply_to": "e.g. 1234567890123456789"}
{"data": {"id": "1234567890123456789","text": "Just shipped v2.0!","edit_history_tweet_ids": ["1234567890123456789"]}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.