What can Claude access through the chiliad connector?

Exactly what the connector lets Claude read and change, what it cannot do, and how access is controlled.

Connecting an AI assistant to the tool that runs your clients' accounts deserves a clear answer about what it can do.

What Claude can do

Scripts — list, read, create and update scripts; archive and restore them; get a script's loader.
Variables and values — declare a script's variables and set values per account.
Accounts — list the Google Ads accounts connected to your workspace; assign and unassign scripts.
Run history — read execution results and error messages.
GAQL — run read-only SELECT queries against one account at a time.
Marketplace — search and install scripts.

What Claude cannot do

Change billing, plans or payment details.
Invite, remove or change the role of team members.
Connect or disconnect Google logins.
Change anything in Google Ads directly. Queries are read-only; changes to an account happen only when a script you deployed runs.

How access is scoped

Your login, your role. The connection is authorized with your chiliad account. Claude has no more access than you do, including limits on which accounts you can see.
One workspace. Claude works in the workspace you approved.
No API keys. Authorization uses a standard sign-in and consent flow, and you can revoke it from Claude's connector settings.
Plan limits apply. Script counts, loader access and history retention are the same as in the dashboard.
Rate limits stop a runaway conversation from hammering your workspace.

Everything leaves a trail

Code saved by Claude appears in the script's version history with Claude as the source. Changes to per-account values appear under config changes. You can compare and restore any of it.

What Claude can do

Scripts — list, read, create and update scripts; archive and restore them; get a script's loader.

Variables and values — declare a script's variables and set values per account.

Accounts — list the Google Ads accounts connected to your workspace; assign and unassign scripts.

Run history — read execution results and error messages.

GAQL — run read-only SELECT queries against one account at a time.

Marketplace — search and install scripts.

How access is scoped

Your login, your role. The connection is authorized with your chiliad account. Claude has no more access than you do, including limits on which accounts you can see.

One workspace. Claude works in the workspace you approved.

No API keys. Authorization uses a standard sign-in and consent flow, and you can revoke it from Claude's connector settings.

Plan limits apply. Script counts, loader access and history retention are the same as in the dashboard.

Rate limits stop a runaway conversation from hammering your workspace.