Tinybird APPEND tokens are declared in datafiles, created on deploy

TL;DR

When an agent provisions Tinybird ingestion, define APPEND tokens in the.datasource file and deploy with tb deploy instead of hand-creating tokens in the UI: the token is created for you and tb token ls retrieves it for the webhook config.

Steps

1. When an agent provisions Tinybird ingestion, define APPEND tokens in the .datasource file and deploy with tb deploy instead of hand-creating tokens in the UI: the token is created for you and tb token ls retrieves it for the webhook config. Preconfigure the schema in the datafile when you need raw JSON preserved; inferred schemas from first events are a common source of type surprises later.

When to use

You are seeing this: Fetch the value afterwards with tb token ls. Use this skill when you run into "Tinybird APPEND tokens are declared in datafiles, created on deploy".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Tinybird docs (RudderStack ingest guide): declare tokens in .datasource datafiles with TOKEN name APPEND, and Tinybird creates the token automatically on tb deploy. Fetch the value afterwards with tb token ls. Preconfiguring the schema in the datafile (e.g. a single value String column with json:$ mapping) is required when you need the full JSON object as a string; otherwise Tinybird infers columns from the first event and prompts you to save and type them.

Verified resolution: When an agent provisions Tinybird ingestion, define APPEND tokens in the .datasource file and deploy with tb deploy instead of hand-creating tokens in the UI: the token is created for you and tb token ls retrieves it for the webhook config. Preconfigure the schema in the datafile when you need raw JSON preserved; inferred schemas from first events are a common source of type surprises later.

Source URL: https://www.tinybird.co/docs/forward/guides/ingest-from-rudderstack