Snapchat Ads

Manage Snapchat advertising from AI agents through the Marketing API. Agents walk the business hierarchy from organizations to ad accounts, ad squads, and ads, and list, create, and update campaigns, with new campaigns defaulting to paused so nothing spends before you activate it.

8 actions OAuth available

Snapchat Ads website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A new row lands in the campaign launch sheet with name, objective, start date, and daily budget

List Organizations and List Ad Accounts resolve which ad account this campaign belongs in

List Campaigns confirms no campaign with this name already exists in the account

Create Campaign writes the campaign, which lands in Paused status by default, spending nothing

The agent posts the campaign summary to the media buyer: objective, schedule, budget in real currency

The media buyer reviews the setup and approves activation, or corrects the budget first

Update Campaign flips the status to Active, and only now does the campaign begin to spend

What This Integration Enables

Snapchat's Marketing API is a hierarchy, not a flat list: organizations hold ad accounts, ad accounts hold campaigns, campaigns hold ad squads, ad squads hold ads. This connector is built for teams that want agents to walk that hierarchy the way a media buyer does, and it takes a position on safety that matters when the output is spend: Create Campaign defaults every new campaign to Paused. An agent can build the entire launch, and nothing costs money until a person or an explicitly approved step activates it. FlowRunner agents use the connector to: - Launch campaigns from spreadsheets, form submissions, or CRM records, configured but paused - Activate, pause, rename, reschedule, or adjust daily budgets with Update Campaign - Audit the full account hierarchy into reporting sheets without anyone exporting anything - React to conversion signals by proposing budget changes, gated by [human-in-the-loop](/concepts/human-in-the-loop) review Note that this is a gated integration: it requires a Snapchat Business account and an approved Marketing API OAuth app before it can be connected.

Without FlowRunner

Launch by clickpath Every campaign is assembled by hand in Ads Manager, and launch day depends on who is at a desk

Budget changes lag the data Performance says raise or cut the budget, but the change waits for someone to notice

The account state lives in one browser tab What is running, at what budget, under which squad, is knowledge held by whoever looked last

With FlowRunner

Launch from the systems you already run A sheet row, a form, or a CRM record becomes a fully configured campaign, paused and ready

Budget moves with review Agents propose budget changes with the evidence attached, and a buyer approves the spend

The account audits itself The whole hierarchy, organizations to ads, lands in a spreadsheet on a schedule

Use Case Scenarios

The launch calendar that builds its own campaigns

The growth team plans launches in [Google Sheets](/integrations/google-sheets). When a new row appears with a campaign name, objective, start time, and budget, the agent resolves the right ad account with List Organizations and List Ad Accounts, checks List Campaigns for a name collision, and calls Create Campaign. The campaign arrives paused. A summary posts to [Slack](/integrations/slack) with the budget converted from micro-currency to dollars, and the media buyer activates it with a single approval that triggers Update Campaign. Launch day stops depending on who is in Ads Manager.

The weekly account audit nobody has to run

On a Monday schedule, the agent walks the hierarchy: List Campaigns for each ad account, List Ad Squads for each campaign, List Ads for each squad. Every row lands in a reporting spreadsheet with status, objective, schedule, and budget. The team opens one sheet and sees exactly what is live, what is paused, and what has been quietly running since March. Finance reconciles the Snapchat invoice against a list that came from the API, not from memory.

Performance-triggered budget moves, with a buyer in the loop

Purchase events from Snapchat Conversions tracking show a campaign converting well below target cost. The agent pulls the campaign with Get Campaign, drafts the proposed change, and posts it for review: current daily budget, proposed daily budget, the conversion evidence, and the campaign's remaining schedule. The buyer approves, and Update Campaign raises the budget that same hour. The same loop runs in reverse when performance falls off: the agent proposes the pause, a person confirms it, and spend stops before the week is out.

Human-in-Loop Highlight

Update Campaign is the action that starts the meter running. Everything else in this connector reads state or creates campaigns that sit paused, but the moment Update Campaign flips a status to Active or raises a daily budget, real money leaves the account, and Snapchat does not refund impressions served against a fat-fingered budget. Budgets here are expressed in micro-currency, where 50000000 means 50 dollars, which is exactly the kind of field a typo turns expensive. So FlowRunner agents treat activation and budget changes as proposals: the agent presents the campaign, the current and proposed values in plain currency, and the evidence behind the change, and the media buyer gives the answer. The campaign build runs at machine speed. The decision to spend belongs to a person.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

8 actions

Organizations

List Organizations Retrieves all Snapchat Business organizations that the connected account can access. Each organization groups one or more ad accounts, and this is the starting point for discovering the IDs everything else needs.

Ad Accounts

List Ad Accounts Retrieves all ad accounts belonging to a specified organization. Ad accounts hold the campaigns, ad squads, and ads; the returned IDs feed campaign listing and creation.

Campaigns

List Campaigns Retrieves all campaigns within a specified ad account, returned in Snapchat's standard envelope. Used to audit existing campaigns, catch name collisions, and obtain campaign IDs.
Get Campaign Retrieves a single campaign by ID. Used to inspect current status, objective, budget, and schedule before proposing a change.
Create Campaign Creates a new campaign in an ad account. Friendly objective labels are mapped to Snapchat's API tokens automatically, and the campaign defaults to Paused status so it does not spend until explicitly activated.
Update Campaign Updates an existing campaign: activate, pause, rename, reschedule, or adjust its daily budget. Only the fields you provide are sent. The action this page's human gate exists for.

Ad Squads

List Ad Squads Retrieves all ad squads within a specified campaign. Ad squads define targeting, budget, schedule, and bidding for the ads they contain.

List Ads Retrieves all ads within a specified ad squad. Each ad links a creative to the squad's targeting and delivery settings, so this is the bottom rung of a full account audit.

Frequently Asked Questions

What can FlowRunner do with Snapchat Ads?

FlowRunner agents can run List Organizations, List Ad Accounts, and List Campaigns in Snapchat Ads, plus 5 more actions.

Does connecting Snapchat Ads to FlowRunner require OAuth?

Yes. Snapchat Ads connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Snapchat Ads trigger a FlowRunner workflow automatically?

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

Start building with Snapchat Ads

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

Start Building Free Talk to us