CRM and sales
Meta Ads for AI agents.
Managed auth, ready-made tools.
Review performance and manage campaigns and ad sets in Meta Ads accounts on behalf of each of your users.
About Meta Ads
With the Meta Ads connector, your agent works in the ad accounts each user can already manage. It can list campaigns and ad sets, pull performance insights, create campaigns and change their status or budget, using only the tools your project allows.
Meta Ads is Meta’s advertising platform for Facebook, Instagram, Messenger and more.
Tools
What your agent can do in Meta Ads.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Meta Ads connection.
-
List ad accounts
Readmeta_ads_list_ad_accountsList the ad accounts the user can access.
-
List campaigns
Readmeta_ads_list_campaignsList the campaigns in an ad account.
-
List ad sets
Readmeta_ads_list_ad_setsList the ad sets in a campaign or account.
-
Get insights
Readmeta_ads_get_insightsGet spend, reach and results for an account, campaign or ad set.
-
Create a campaign
Writemeta_ads_create_campaignCreate a campaign with a name, objective and status.
-
Update a campaign
Writemeta_ads_update_campaignChange a campaign's name, status or budget.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Meta Ads, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read campaigns and insights, and switch off
meta_ads_update_campaignso it can never pause a campaign or change a budget. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example insights but not campaign changes. A call outside them is refused.
Get started
Connect Meta Ads
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Meta Ads
Each end user authorizes their own Meta Ads account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Meta Ads account, once. const connection = await agent200 .user("user_123") .connect("meta_ads"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Meta Ads tools
Name the user, the model and the tools. The model decides which Meta Ads tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "How did our Instagram campaigns do last week", tools: ["meta_ads"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Meta's own sign-in page. You never see or store their Meta password.
-
What access is requested
The scopes the connection needs, such as reading ads or managing ads, listed on Meta's authorization screen. Users can remove the app later from their Meta account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Meta Ads connector and how to use it.
Connector: Meta Ads, through Agent200. In code: "meta_ads". What it does: Review performance and manage campaigns and ad sets in Meta Ads accounts on behalf of each of your users. Page: https://www.agent200.com/connectors/meta-ads/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Meta Ads's own page, through the authorization link Agent200 returns. Never ask a user for a Meta Ads password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: meta_ads_list_ad_accounts, meta_ads_list_campaigns, meta_ads_list_ad_sets, meta_ads_get_insights. Write tools: meta_ads_create_campaign, meta_ads_update_campaign. Name "meta_ads" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/meta-ads/framework/claude/ https://www.agent200.com/connectors/meta-ads/framework/chatgpt/ https://www.agent200.com/connectors/meta-ads/framework/claude-code/ https://www.agent200.com/connectors/meta-ads/framework/muse/ https://www.agent200.com/connectors/meta-ads/framework/grok-bot/ https://www.agent200.com/connectors/meta-ads/framework/openai-dots/ https://www.agent200.com/connectors/meta-ads/framework/claude-duet/ https://www.agent200.com/connectors/meta-ads/framework/hermes-agent/ https://www.agent200.com/connectors/meta-ads/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/meta-ads.md
Guides
Use Meta Ads with the AI you build on.
Step-by-step setup for Meta Ads with a specific model, assistant or agent framework.
-
Meta Ads + Claude
How to connect Meta Ads to Claude
-
Meta Ads + ChatGPT
How to connect Meta Ads to ChatGPT
-
Meta Ads + Claude Code
How to connect Meta Ads to Claude Code
-
Meta Ads + Muse
How to connect Meta Ads to Muse
-
Meta Ads + Grok Bot
How to connect Meta Ads to Grok Bot
-
Meta Ads + OpenAI Dots
How to connect Meta Ads to OpenAI Dots
-
Meta Ads + Claude Duet
How to connect Meta Ads to Claude Duet
-
Meta Ads + Hermes Agent
How to connect Meta Ads to Hermes Agent
-
Meta Ads + OpenClaw
How to connect Meta Ads to OpenClaw
FAQ
Meta Ads and Agent200, answered.
Who handles the Meta Ads OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Meta Ads.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Meta Ads connection, never another user's. It cannot reach anything the user or Meta Ads has not authorized.
Can I limit what my agent can do in Meta Ads?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.