Facebook Custom Audiences
AdvertisingManage Meta ad targeting from your workflows. Agents create and maintain Facebook Custom Audiences, add or remove hashed user lists, and keep ad account audiences synced with your CRM data.
What This Integration Enables
Ad targeting is only as good as the list behind it, and customer lists rot fast: new buyers missing, churned customers still targeted, opt-outs unhonored. This connector makes Meta Custom Audiences a live reflection of your actual customer data. FlowRunner agents create Customer File audiences, keep membership synced from the CRM and the store, and honor opt-outs on the same schedule, with Meta's hashing requirement handled automatically: you pass plain emails, the connector normalizes and SHA-256 hashes them before anything leaves the flow. - Build audiences from opted-in customer emails and populate them programmatically - Keep retargeting audiences synced with CRM and storefront data on a schedule - Suppress opt-outs by email without touching the rest of the audience - Check approximate size and delivery status before campaigns launch - Retire unused audiences deliberately, with the deletion gated by a person Note the gating: this integration requires a Meta app with the ads_management permission, access to a Business ad account, and acceptance of Meta's Custom Audience terms on that account. Audience sync is also where ad operations and privacy operations collide, and the collision is best handled by orchestration rather than heroics. The same flow that grows the audience is the flow that shrinks it, which means opt-out handling is not a separate compliance project bolted on later; it is the other half of a loop that already runs nightly, with a log that already exists. FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate completes the picture by keeping the one destructive operation, audience deletion, behind a person who can see what a campaign is about to lose.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The retargeting audience that never goes stale
New customers land in [Shopify](/integrations/shopify) all day. A nightly flow collects them and calls Add Users on the store's retargeting audience, then pulls the day's unsubscribes and calls Remove Users. Get Custom Audience confirms the size bounds moved the right direction, and the digest posts to the growth channel. The audience Meta targets tomorrow reflects the store as of last night, not as of whenever someone last remembered to upload a CSV.
A lookalike seed built from the CRM's best segment
Ahead of a prospecting push, the agent pulls qualified, opted-in contacts from [HubSpot](/integrations/hubspot), calls Create Custom Audience for a fresh Customer File audience, and populates it with Add Users. An hour later, once matching completes, Get Custom Audience verifies the audience is ready and delivering, and the team builds its lookalike from a seed that is actually the current definition of a good customer, not an export from two quarters ago.
Opt-outs with a paper trail
A preference form in [Typeform](/integrations/typeform) captures opt-outs. Each submission fires Remove Users against every audience the email could appear in, discovered via List Custom Audiences, and appends a row to [Google Sheets](/integrations/google-sheets): email, audiences suppressed, timestamp, request source. When the privacy question arrives, months later, in legal language, the answer is a filtered spreadsheet instead of a scramble through Ads Manager history.
Human-in-Loop Highlight
Delete Custom Audience removes the audience and its entire membership permanently, and any ad set targeting it simply stops delivering. The membership is the unrecoverable part: a Customer File audience is the accumulated result of months of uploads, matched against Meta's graph, and Meta never exposes the member list back to you, so there is no export to restore from. Delete the wrong audience mid-campaign and live ad sets go dark while the rebuilt replacement spends up to an hour re-matching whatever emails you still hold. So cleanup flows in FlowRunner only nominate. The agent lists audiences with List Custom Audiences, flags candidates no active campaign references, and presents each with its name, approximate size bounds, and status. The audience owner confirms which ones die, and only then does the delete run. When the goal is dropping specific people, the agent reaches for Remove Users instead, because trimming members is reversible and erasing an audience is not.
Agent Capabilities
6 actionsCustom Audiences
4- List Custom Audiences Lists an ad account's Custom Audiences with pagination: ID, name, subtype, approximate size, and status. The discovery step behind sync flows, suppression sweeps, and cleanup nominations.
- Create Custom Audience Creates a new empty Customer File audience in the ad account and returns its ID for population with Add Users. Subtype is fixed to CUSTOM and the customer file source defaults to User Provided Only.
- Get Custom Audience Retrieves one audience's name, description, subtype, approximate size bounds, and delivery status. Meta never exposes exact counts, so the bounds are the health signal flows check before launches.
- Delete Custom Audience Permanently deletes an audience and its membership; ad sets targeting it stop delivering. Cannot be undone, and the operation this page's human gate exists for.
Membership
2- Add Users Adds members by plain email address, with normalization and SHA-256 hashing handled automatically before upload. Returns received and invalid counts. New members take up to an hour to match and become targetable.
- Remove Users Removes members by plain email address with the same automatic hashing. The surgical tool for opt-outs and suppressions that leaves the rest of the audience intact.
Frequently Asked Questions
What can FlowRunner do with Facebook Custom Audiences?
FlowRunner agents can run List Custom Audiences, Create Custom Audience, and Get Custom Audience in Facebook Custom Audiences, plus 3 more actions.
Does connecting Facebook Custom Audiences to FlowRunner require OAuth?
No. Facebook Custom Audiences connects to FlowRunner with an API key, no OAuth flow required.
Can Facebook Custom Audiences trigger a FlowRunner workflow automatically?
Facebook Custom Audiences doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Facebook Custom Audiences
$100 in credits. No card required. Connect in minutes.