Start free
ActionTinybirdUpdated June 2026

How do I send events to a Tinybird data source?

Short answer: You can ingest events in Tinybird by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Tinybird Ingest Events 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.

Ingest Events in Tinybird — start free All 2 Tinybird actions
Ingest Events 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.

FieldTypeRequiredDescription
Data Source Name
datasource
stringRequiredData Source Name
Events (NDJSON)
events
jsonRequiredEvents (NDJSON). (JSON object). e.g. "{"timestamp":"2026-04-11T10:00:00Z","event":"page_view","page":"/home"}"
Sample request
{
  "datasource": "{{trigger.datasource}}",
  "events": "{\"timestamp\":\"2026-04-11T10:00:00Z\",\"event\":\"page_view\",\"page\":\"/home\"}"
}
Returns
{
  "successful_rows": 1,
  "quarantined_rows": 0
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Ingest Events.

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

Gmail → Tinybird
1 Gmail triggers
Slack → Tinybird
13 Slack triggers
Google Sheets → Tinybird
2 Google Sheets triggers
HubSpot → Tinybird
18 HubSpot triggers
FAQ

Questions about Ingest Events.

What does the Ingest Events action do in Tinybird?
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.
What inputs does Ingest Events require?
Required: Data Source Name, Events (NDJSON). 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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Ingest Events support batch operations?
Yes. Run Ingest Events inside a Loop node to process arrays. TinyCommand handles Tinybird's rate limits automatically so you don't have to throttle manually.
More actions

Other Tinybird actions.

Action
Query API Endpoint
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.
Ingest Events in Tinybird — start free