Short answer: Drop the "X (Twitter) → Search Tweets" 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 |
|---|---|---|---|
Search Query query | string | Required | Search query (max 512 chars). Supports operators: from:, to:, is:retweet, has:media, lang:, etc. |
Max Results max_results | number | Optional | Number of results (10-100) |
Sort Order sort_order | options | Optional | Sort Order. Options: Most Recent, Most Relevant |
{"query": "e.g. from:elonmusk AI","max_results": "{{trigger.max_results}}","sort_order": "{{trigger.sort_order}}"}
{"data": [{"id": "123","text": "Hello world","author_id": "456","created_at": "2026-04-19T10:00:00Z","public_metrics": {"like_count": 10,"reply_count": 2,"retweet_count": 5}}],"meta": {"next_token": "abc123","result_count": 10}}
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.