Short answer: Drop the "Twitter / X → 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 |
|---|---|---|---|
Query query | string | Required | Query. e.g. "#AI OR machine learning" |
Max Results max_results | number | Optional | Max Results |
{"query": "#AI OR machine learning","max_results": "{{trigger.max_results}}"}
{"data": [{"id": "tweet123","text": "AI is amazing...","created_at": "2026-04-11T10:00:00Z","public_metrics": {"like_count": 20,"retweet_count": 5}}],"meta": {"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.