ActionTinybirdUpdated September 2026

How do I query a published Tinybird API?

Short answer: You can query api endpoint in Tinybird by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Tinybird Query API Endpoint action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Query API Endpoint in Tinybird — start free All 2 Tinybird actions

Query API Endpoint in Tinybird — start free

Inputs

The fields this action accepts.

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}"

Sample request

{
  "pipeName": "my_analytics_endpoint",
  "params": "{\"date_from\":\"2026-04-01\",\"limit\":10}"
}

Returns

{
  "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.

Triggered by

Apps that pair well as the trigger for Query API Endpoint.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Tinybird

2 Google Sheets triggers

HubSpot → Tinybird

18 HubSpot triggers

FAQ

Questions about Query API Endpoint.

What does the Query API Endpoint action do in Tinybird?

Queries a published Tinybird API endpoint with the supplied parameters and returns the JSON response. Use it to embed real-time analytics or to drive in-app charts.

What inputs does Query API Endpoint require?

Required: Pipe Name. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Tinybird returns an error?

The run history shows the failed step with its input and the error message Tinybird returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Query API Endpoint support batch operations?

Run Query API Endpoint inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Tinybird's rate limits.

More actions

Other Tinybird actions.

Action

Ingest Events

Sends one or more events to a Tinybird Data Source via the Events API for low-latency analytical ingestion. Use it for product analytics, audit logs, or anything you'll query through Pipes later.

Query API Endpoint in Tinybird — start free