Short answer: Drop the "Tinybird → Ingest Events" 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 |
|---|---|---|---|
Data Source Name datasource | string | Required | Data Source Name |
Events (NDJSON) events | json | Required | Events (NDJSON). (JSON object). e.g. "{"timestamp":"2026-04-11T10:00:00Z","event":"page_view","page":"/home"}" |
{"datasource": "{{trigger.datasource}}","events": "{\"timestamp\":\"2026-04-11T10:00:00Z\",\"event\":\"page_view\",\"page\":\"/home\"}"}
{"successful_rows": 1,"quarantined_rows": 0}
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.