Short answer: Drop the "X (Twitter) → 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 | 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. |
{"text": "{{trigger.text}}","in_reply_to_tweet_id": "{{trigger.in_reply_to_tweet_id}}","quote_tweet_id": "{{trigger.quote_tweet_id}}"}
{"data": {"id": "1234567890","text": "Hello world!"}}
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.