TikTok Audiences

Manage TikTok Ads custom audiences with AI agents. Agents create audiences, sync CRM segments and subscribers in by email, remove churned or unsubscribed users to keep targeting compliant, and audit audience size and status. Emails are SHA-256 hashed before they leave FlowRunner.

5 actions API key available

TikTok Audiences website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

The nightly suppression sync starts after the email platform closes its day

The agent pulls the day's unsubscribes and churned customers from the CRM and email tool

List Audiences confirms which custom audiences are active and currently used in targeting

Apply Users to Audience runs with Remove, purging the suppressed emails, hashed before they leave FlowRunner, from every targeting audience

The day's new opt-in converters stage as an Add batch for the retargeting audience

The growth lead approves the Add batch, because expanding who the brand targets is a spend and compliance decision

The audience-ops channel gets the counts: removed, added, and each audience's latest size and status

What This Integration Enables

A custom audience is only as good as its last sync, and most TikTok audiences are snapshots: uploaded once, decaying daily, and quietly retaining people who opted out. Decay costs twice, once in wasted spend on lapsed customers and once in compliance exposure on suppressed ones. This connector makes audience membership a maintained property. FlowRunner agents create EMAIL_SHA256 customer-file audiences, stream adds and removes from your CRM and email platforms, and audit size and status across the account, with hashing handled inside FlowRunner so raw emails never leave. - Sync subscribers, purchasers, and CRM segments into custom audiences for targeting or exclusion - Add newly converted or opted-in users to retargeting audiences as they arrive - Remove unsubscribed, churned, and suppressed users to keep targeting clean and compliant - Provision fresh, empty audiences on demand and populate them from a flow, per campaign or per segment - Audit every audience's size, type, calculation type, and validity status across the whole ad account The asynchronous matching model shapes how agents verify their own work: an Apply Users call returns before TikTok finishes matching, so cover_num lags the sync, and a new audience needs a minimum match size before ads can deliver to it. FlowRunner agents build the follow-up check into the flow, confirming size movement with Get Audiences the next day instead of declaring victory at the API response. Audience membership decides who a brand spends money to reach, so the operations that expand or destroy audiences run behind FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gates.

Without FlowRunner

Audiences frozen at upload time The CSV uploaded in March still defines who sees the ads in July

Suppression lag Unsubscribed and churned users keep seeing retargeting ads for weeks, which they notice

Raw emails in transit Someone exports customer emails and uploads them by hand, with all the handling risk that implies

With FlowRunner

Audiences track the CRM daily Adds and removes flow nightly, so targeting mirrors the live customer base

Suppression within a day Opt-outs leave every targeting audience on the next sync, by design

Hashes leave, emails do not Every address is trimmed, lowercased, and SHA-256 hashed inside FlowRunner before TikTok sees it

Use Case Scenarios

The retargeting audience that mirrors the CRM

The agent pulls the high-intent segment from [HubSpot](/integrations/hubspot), creates a dedicated audience with Create Audience, and populates it with Apply Users to Audience in Add mode. From then on, a nightly diff keeps it current: new segment members add, exits remove. TikTok's matching runs asynchronously, so the agent checks Get Audiences the next day to confirm the size moved and the audience stays valid for delivery.

Suppression as an enforced invariant

Opt-outs and churn events accumulate in [Klaviyo](/integrations/klaviyo) and the CRM. Every night, the agent assembles the suppression list and runs Apply Users to Audience with Remove across every active targeting audience from List Audiences. No approval needed: removing people who opted out is the compliance default, and the agent logs each batch for the audit trail. The embarrassing ad that follows a customer who unsubscribed stops happening, and when a privacy request arrives, the log shows exactly when the removal ran and against which audiences.

The audience account audit

Quarters of campaigns leave behind a sediment of stale audiences. The agent runs List Audiences page by page, pulls detail with Get Audiences, and writes name, size, type, status, and rejection reasons to [Google Sheets](/integrations/google-sheets). Audiences that are invalid, rejected, or below usable match size get flagged. The cleanup list goes to the growth lead, who marks which ones Delete Audiences may permanently remove, and the agent executes only that marked set. The account ends the quarter with audiences someone can actually name and defend.

Human-in-Loop Highlight

Delete Audiences is permanent: TikTok will reject deletion of an audience an active ad group is using, but everything else it removes is gone, including audiences that took months of syncing to build to usable match size. And Apply Users to Audience in Add mode is a quieter kind of consequential, because every address added expands who the brand pays to target, which is both a budget decision and a consent question. FlowRunner agents split the difference by direction. Removes run autonomously, since purging opted-out users is the always-correct default. Adds above a threshold, and every deletion, stage for the growth lead with the specifics: audience name, current size from Get Audiences, batch count, and where the emails came from. The nightly hygiene runs itself. The actions that grow targeting or erase an asset wait for a person.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

Audiences

List Audiences Lists the advertiser account's custom audiences, newest first, with id, name, size, type, calculation type, and status. Pages up to 100 per call with total counts in page_info. The account-wide inventory behind audits and sweeps.
Get Audiences Retrieves full details for up to 100 audiences by id, including validity status, rejection reasons, and timestamps. The verification read that confirms syncs actually landed, since matching is asynchronous.
Create Audience Creates a new, empty customer-file audience with the EMAIL_SHA256 calculation type, ready to populate by hashed email. Returns the new custom_audience_id.
Delete Audiences Permanently deletes up to 100 audiences by id. Cannot be undone, and audiences in use by active ad groups may be rejected. The destructive operation this page's gate reserves for a person.

Apply Users

Apply Users to Audience Adds or removes users in an EMAIL_SHA256 audience by email match. Plain addresses are trimmed, lowercased, and SHA-256 hashed inside FlowRunner; pre-hashed 64-character values pass through unchanged. Add mode grows targeting and runs gated; Remove mode enforces suppression and runs free.

Frequently Asked Questions

What can FlowRunner do with TikTok Audiences?

FlowRunner agents can run List Audiences, Get Audiences, and Create Audience in TikTok Audiences, plus 2 more actions.

Does connecting TikTok Audiences to FlowRunner require OAuth?

No. TikTok Audiences connects to FlowRunner with an API key, no OAuth flow required.

Can TikTok Audiences trigger a FlowRunner workflow automatically?

TikTok Audiences doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with TikTok Audiences

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us