Integrations · Meta Ads
A Guild agent can create, update, and report on Meta Ads campaigns without a human opening Ads Manager. Guild stores the Meta Ads API key server-side so agent code never sees it, and credential policies let you restrict exactly which operations each agent may run.
Book a demo
See how teams govern agents that use Meta Ads.
Talk to sales
Get access to Guild, then connect Meta Ads to your first agent.
What the Meta Ads integration exposes
The integration uses the Meta Marketing API v26.0. Tools cover ad accounts, campaigns, ad sets, ads, and performance insights. Agents can create campaigns (paused by default unless status is ACTIVE), create ad sets with billing event and optimization goal, create ads from an existing creative, update delivery and budgets with a sparse update, and retrieve synchronous stats at the account or object level. Tools are named with themeta_ads_ prefix.
How it works
1
Connect your Meta Ads credential
Go to Access & setup > Credentials, click Connect, select meta-ads, and paste your API key. Guild sends it as a bearer token in the Authorization header on every agent request.
2
Scope the credential
By default the credential serves every workspace the account owns. You can scope it to one workspace, one member, or one agent from the same Credentials page. See Credentials for the full scoping options.
3
Add the tools to your agent
Import MetaAdsTools from the integration package and spread it into your agent’s tools object. Use pick() to include only the specific meta_ads_ tools your agent needs.
Why Meta Ads access needs governing
Setting an ad object’s status to ACTIVE resumes delivery and can spend budget immediately. Guild’s credential proxy enforces credential policies before any request reaches Meta, so you can write DENY rules that block mutating operations like meta_ads_create_campaign or meta_ads_update_ad_object for agents that only need to read insights. A DENY rule always takes precedence over an ALLOW rule, and agents cannot bypass the check because the credential is injected server-side only after the policy passes. Credentials are stored and resolved by Guild, not by agent code. You can dedicate a credential to one agent, grant an existing credential to a specific agent, or restrict a workspace to its own credentials so shared account credentials never reach it. All of this is visible in the Credentials page, which shows each credential’s scope alongside its connected integration.About the Meta Ads integration
Agents can create and update campaigns, ad sets, and ads across Meta ad accounts. They can retrieve account-level and object-level performance insights synchronously. Agents can also list and manage existing ad objects using the Meta Marketing API v26.0. The integration isguildai~meta-ads.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect Meta Ads
In Guild, go to Access & setup > Credentials, click Connect, select meta-ads, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with themeta_ads_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~meta-ads:
Frequently asked questions
Can an agent create an ad without an existing creative?
Can an agent create an ad without an existing creative?
No. The meta_ads_create_ad tool requires that creative.creative_id already exists before the call is made.
Does Guild support webhook events from Meta Ads?
Does Guild support webhook events from Meta Ads?
Not yet. The catalog entry for guildai~meta-ads lists no webhook events, so agents cannot react to Meta-side events through Guild triggers.
How do I stop one agent from spending budget while letting another read reports?
How do I stop one agent from spending budget while letting another read reports?
Write a DENY rule in credential policies that blocks meta_ads_update_ad_object and meta_ads_create_campaign for the read-only agent, then scope an ALLOW rule to the reporting agent. The proxy enforces this before any request reaches Meta.
Can I use the same Meta Ads credential across multiple workspaces?
Can I use the same Meta Ads credential across multiple workspaces?
Yes. An account-scoped credential serves every workspace the account owns by default. If a workspace has Use only credentials scoped to this workspace turned on in its settings, it will not use the shared account credential and needs its own.
Put a governed agent on Meta Ads this week
Book a demo
See how teams govern agents that use Meta Ads.
Talk to sales
Get access to Guild, then connect Meta Ads to your first agent.