Integration · Research and analyze

Dataslayer and Meteor AI agents

Connect Dataslayer to a Met: ask in plain language for Google Ads, Facebook Ads and other data from your sources with the official MCP.

Book a demo See every integration

How does Dataslayer connect to Meteor?

With the Dataslayer ready connector, your Met queries the marketing and analytics data you have connected in Dataslayer, with 12 tools. You ask for something like "clicks by Google Ads campaign last week" and Dataslayer resolves the source, accounts, fields and dates and runs the query. The Met also checks which sources and accounts you have, follows in-progress queries by their task_id and checks your plan and usage. The shared limit of 50 API calls per day applies. Alerts and scheduled transfers start off. Your Dataslayer plan pays for the service.

What it automates

What a Meteor Met does with Dataslayer

Ask for data in plain language

You write to the Met on WhatsApp "clicks by Google Ads campaign for the last 7 days". The Met passes the request to Dataslayer, which resolves the source, accounts, fields and dates and runs the query.

Know what you have connected

The Met tells you how many sources you have connected in Dataslayer and which accounts, properties or sites each one has.

Follow an in-progress query

If a query comes back in progress, the Met gives you its task_id. When you ask whether it finished, it checks, and if the result comes in parts, it brings the next page.

Watch the daily cap

The Met checks your plan, your limits and your usage, so you know where you stand against the 50 API calls per day.

Query special sources

Before querying Google Trends, PageSpeed or Keyword Planner, the Met checks how data is requested from each of those sources.

12 tools

Everything your Met can ask Dataslayer for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`get_available_datasources`	Shows which data sources your Dataslayer plan allows, or which you could add by upgrading: what is allowed, not what is connected.
`get_hub_connections`	Shows which and how many data sources you have connected.
`get_available_fields_by_datasource`	Shows which metrics, dimensions or options a data source has.
`get_available_connections_and_accounts_info_by_datasource`	Shows which accounts, properties or sites you have in a data source, or the schema of a database connection.
`natural_to_data`	Gets marketing or analytics data from a plain language request: it resolves the source, accounts, fields and dates and runs the query.
`dataslayer_subscription_information`	Shows your Dataslayer plan, its limits, your usage, the renewal and the company.
`manage_alerts`	Creates, updates, deletes, lists or runs an AI alert, or shows its execution history. It starts off.
`manage_data_transfer_schedules`	Creates, updates, deletes, lists or runs a scheduled data transfer to BigQuery, AWS Redshift, AWS S3, Snowflake, Google Cloud Storage, a database, Azure SQL or Azure Storage, or shows its history. It starts off.
`check_task_id`	Checks by its task_id whether a query that came back "in progress" has finished.
`get_schedules_from_user`	Shows which Google Sheets or Excel schedules you have saved; read only.
`get_special_datasource_call_type_hints_tool`	Explains how to request data from special sources: Google Trends, PageSpeed, Keyword Planner, public Instagram, Facebook and YouTube data, and AppLovin.
`get_next_paginated_result`	Returns the next page of a query result, by its task_id.

The limits

What the Dataslayer integration does NOT do

We would rather say it here than have you find out during rollout.

It does not create alerts or scheduled transfers out of the box: those two actions start off because Dataslayer marks them as destructive. The admin decides in Connections whether to turn them on.
It does not go over the Dataslayer cap: there is a shared limit of 50 API calls per day, no matter which client makes them.
It does not create or change Google Sheets or Excel schedules: it only lists them.
It does not connect new sources. Data sources are connected in Dataslayer.
It does not see your marketing platforms' credentials: they do not leave Dataslayer.
It does not ask you for confirmation in the chat before writing: the admin decides in Connections which actions stay on.

Before you start

What you need to connect Dataslayer

1

An active Dataslayer account

With at least one data source connected in Dataslayer, such as Google Ads or Facebook Ads.
2

Connect it in Met

In Met, open Connections → Dataslayer → Connect. A Dataslayer window opens so you sign in and authorize Met.

Frequently asked questions

Questions about Dataslayer and Meteor

Dataslayer applies a shared limit of 50 API calls per day, no matter which client makes them. The Met can check your usage in your plan information.

Because it is still running. Dataslayer returns a task_id; when you ask, the Met uses it to check whether it finished, and if the result has more pages, it brings you the next one.

Dataslayer has scheduled transfers to those destinations, but that action starts off. The admin decides in Connections whether to turn it on.

You do, with your Dataslayer plan. Meteor does not resell the service, and Met does not charge for the queries your Met makes to Dataslayer.

Step by step