Short answer: Drop the "Tinybird → Query API Endpoint" 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 |
|---|---|---|---|
Pipe Name pipeName | string | Required | Pipe Name. e.g. "my_analytics_endpoint" |
Parameters params | json | Optional | Parameters. (JSON object). e.g. "{"date_from":"2026-04-01","limit":10}" |
{"pipeName": "my_analytics_endpoint","params": "{\"date_from\":\"2026-04-01\",\"limit\":10}"}
{"data": [{"date": "2026-04-11","users": 800,"pageviews": 1500}],"rows": 1,"statistics": {"elapsed": 0.01,"rows_read": 1000}}
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.