Integration · Databases
AI agents for Tinybird
Query a Tinybird workspace: call its published API endpoints with parameters, run read-only SQL over data sources and pipes, list data sources and pipes with their schemas and sizes, send events into a data source.
- Actions
- 8
- Read
- 6
- Write
- 2
Actions
What your agents can do in Tinybird
Query a Tinybird workspace: call its published API endpoints with parameters, run read-only SQL over data sources and pipes, list data sources and pipes with their schemas and sizes, send events into a data source, and delete rows that match a condition. Works in every Tinybird region.
Read 6
Look things up. Nothing changes.
Call an API endpoint
Calls one of the workspace's published API endpoints (a pipe published as an endpoint) with its parameters, and returns its rows.
Run read-only SQL
Runs a ClickHouse SELECT over the workspace's data sources and pipes (by name) through the Query API and returns the rows as JSON.
List data sources
Lists the data sources (tables) the token can read, with their schemas.
Get a data source
Reads one data source by name or ID: id, name, type, engine, columns, statistics (estimated bytes and row_count), used_by and its dates.
List pipes
Lists the pipes the token can read, with their nodes' SQL.
Get a job
Reads a job by ID (a delete, an import, a copy or a populate).
Write 2
Create, change or send.
Send an event
Appends one row to a data source through the Events API: event maps the data source's JSON paths to values, like {"timestamp": "2026-10-31 10:00:00", "user_id": "u_123", "action": "signup"}.
Delete rowsDeletes data
Deletes, for good, the rows of a data source that match a SQL condition, like country = 'ES' AND created_at < '2025-01-01'.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Tinybird account.
What you enter
- Token
Settings
- API host
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Tinybird data
Ask a question in plain words. The agent can call an API endpoint, run read-only SQL or list data sources in Tinybird, then answers with what it found.
- 02
Let an agent update Tinybird
Have the agent send an event or delete rows in Tinybird as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Tinybird and Slack: it can call an API endpoint in Tinybird and post a summary to a Slack channel in the same run.
FAQ
Tinybird and MyDeepAgents
Can MyDeepAgents connect to Tinybird?
Yes. The Tinybird connector has 8 actions: 6 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Tinybird?
Paste an API key from your Tinybird account. You'll need: Token. The connection also asks for: API host. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Tinybird without asking?
Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Tinybird in workflows as well as agents?
Yes. Every Tinybird action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Tinybird to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.