Meta Ads
Turn orders and customer changes into the right Meta Ads audiences and campaigns, with a person approving what goes out.
24 ways to read, 7 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Meta Ads, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create paused ad setApproval by rule
- Create paused adApproval by rule
- List ad account activityRead
Example flow
- Meta Ads · List ad account activityDone
- Meta Ads · Create paused ad setNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Meta Ads.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Meta Ads
- Meta Ads's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Meta test account before you go live.
For developers
Technical detail
Read Meta ad accounts, campaigns, ad sets, ads, creatives, insights, audiences, pixels, activity and leads; create paused campaigns, ad sets and ads; send Conversions API events.
Meta API docs- Source actions
- 24
- Destination actions
- 7
- Data types
- 16
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Activities1
- List ad account activitySourceIncremental
Change history of the ad account: who changed which campaign, ad set, ad or budget, and when.
Ad accounts2
- Get ad accountSource
The configured ad account's name, status, currency, time zone and spend.
- List ad accountsSource
Ad accounts the access token can use, with status and currency.
Ad creatives2
- Get ad creativeSource
One creative by ID.
- List ad creativesSource
Creatives in the ad account with copy, image, call to action and story IDs.
Ad images1
- List ad imagesSource
Images in the ad account library, keyed by image hash.
Ad leads1
- List leads for an adSourceIncremental
Lead ads submissions attributed to one ad.
Ad sets4
- Create paused ad setDestinationNot retried automaticallyApproval before production
Creates an ad set in PAUSED status with an explicit budget and targeting.
- Get ad setSource
An ad set by ID.
- List ad setsSourceIncremental
Ad sets with budgets, optimisation goal, billing event and targeting.
- Change ad set status or budgetDestinationProvider duplicate protectionApproval before production
Activates, pauses or renames an ad set, or sets an explicit budget, bid or end time.
Ads4
- Create paused adDestinationNot retried automaticallyApproval before production
Creates an ad in PAUSED status from an existing creative.
- Get adSource
An ad by ID.
- List adsSourceIncremental
Ads with status and creative.
- Change ad statusDestinationProvider duplicate protectionApproval before production
Activates, pauses or renames an ad.
Campaigns4
- Create paused campaignDestinationNot retried automaticallyApproval before production
Creates a campaign in PAUSED status; it does not deliver until activated.
- Get campaignSource
A campaign by ID.
- List campaignsSource
Campaigns in the ad account with objective, status and budgets.
- Change campaign status or budgetDestinationProvider duplicate protectionApproval before production
Activates, pauses or renames a campaign, or sets an explicit budget or spend cap.
Conversion events1
- Send Conversions API eventDestinationProvider duplicate protectionApproval before production
Sends one server event to the configured pixel (dataset); Meta deduplicates on eventId and event name.
Custom audiences2
- Get custom audienceSource
One custom audience with size bounds and delivery status.
- List custom audiencesSource
Custom audiences with subtype, size bounds and delivery status (read-only).
Insights1
- Get ad insightsSource
Performance metrics for the ad account at account, campaign, ad set or ad level over a bounded period.
Lead forms2
- Get lead formSource
One lead form with its questions and lead count.
- List lead formsSource
Lead generation forms on a Page.
Leads2
- Get leadSource
One lead ads submission with answers and ad attribution.
- List leadsSourceIncremental
Lead ads submissions for a form, with answers and ad attribution.
Object insights1
- Get insights for a campaign, ad set or adSource
Performance metrics for one campaign, ad set or ad, optionally broken down to a lower level, over a bounded period.
Pixels2
- Get pixel (dataset)Source
One pixel by ID, defaulting to the connection's pixel.
- List pixels (datasets)Source
Pixels available to the ad account, with last fired time and matching settings.
Saved audiences1
- List saved audiencesSource
Saved targeting audiences with size estimates and targeting specs.
Access and limits
- Authentication
- System user access token (bearer)
- Plans and access
- Marketing API access through a Meta app with ads_read/ads_management (Standard Access for production volumes). Use a system user token assigned to the ad account (and Page for lead ads) with ads_read, ads_management, leads_retrieval and pages permissions.
- Test environment
- Sandbox ad accounts are available from the app's Marketing API tools.
- Rate limits
- Business Use Case rate limits per ad account, reported in X-Business-Use-Case-Usage headers; error codes 17, 80000-80014 indicate throttling.
- Pagination
- Graph API cursor paging with limit and after while paging.next is present.
- Provider events
- Page leadgen webhooks for new lead ads submissions. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Pinned to Graph API v26.0.
- Campaigns, ad sets and ads are always created PAUSED; activation and budget changes need explicit inputs.
- Intentionally excluded: deleting or archiving campaigns, ad sets, ads, creatives, audiences or pixels; creating or editing creatives, custom audiences (including Customer Match uploads), saved audiences and lead forms; and any new write that creates or activates spend.
- Ad account activity fields beyond event_type, event_time, actor_name, object_type and date_time_in_timezone (actor_id, object_id, object_name, extra_data, translated_event_type) are mapped when present; the activities guide does not list them all.
- Listing saved audiences uses the ad account saved_audiences edge; the SavedAudience node is documented, but the edge's field set was not confirmed in the guide.
- Pixel reads never request the pixel base code.
- The access token is sent in the Authorization header; appsecret_proof (sent as a parameter) is not supported, so 'Require app secret' must be off.
- Conversions API events are deduplicated by Meta on event_id and event_name within 48 hours; send a stable eventId.
- Insights use bounded date presets or explicit ranges; maximum and data_maximum presets are not offered.
- Lead forms need a token with access to the Page; Meta may require a Page access token for leadgen_forms.
Developer reference
- Create the Meta credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Meta Ads, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/meta-ads and the Connections API.