Skip to content

Automation · Content and publishing

Build a Meta Ads campaign that moves the conversation to WhatsApp

An AI agent builds a Meta Ads campaign that opens WhatsApp, leaves it paused for review and measures conversations started, not sales.

How do I build a Meta Ads campaign that opens WhatsApp without assembling each part separately?

A Met connected to Meta Ads first identifies the ad account and checks which campaigns already exist so it does not split the budget with a duplicate. It then picks the Facebook Page, takes the image from a public URL and creates the campaign, ad set, creative and ad that open the WhatsApp number connected to the workspace in a single call. All four objects start paused and the response returns their identifiers. Before any money is spent, the Met shows the account, Page, number and daily budget; it only calls activate after a person says yes at that moment. Once the campaign has delivered, it reads spend, impressions, clicks, reach, cost per result and conversations started. It does not attribute sales or send conversion events to Meta.

What starts it

When someone asks for it

The recipe starts when a person asks the Met for the campaign inside Meteor and supplies the offer, daily budget, audience, Page and image. A prospective customer's message does not trigger creation: WhatsApp is the destination of the ad, not the channel from which spending is authorized.

A manual task: someone on the team runs it with a button, or asks the Met for it in chat.

Who runs it

Digital advertising Met

Social team

This is not a named, seeded Met. It is an internal Met that works with whoever manages the ad account, not with the person arriving from the ad. Its job is to build the campaign on the right account, stop before activating spend and bring back the numbers Meta actually reports.

What you need connected

7 steps · 8 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

  1. 1

    Pick the account and make sure the campaign does not exist

    The Met lists the available ad accounts with their currency, time zone and status, and works on the identifier the person confirms. It then lists that account's campaigns, including paused ones, before creating another. A campaign for the same product and audience is not a harmless draft: it can divide both budget and learning between two objects. If one already exists, the Met returns its name, status and identifier and asks whether to adjust it or whether a new one is truly needed.

  2. 2

    Choose the Page that signs the ad

    Every campaign needs a Facebook Page as its identity. The listing returns the Pages the connection can reach and, when present, the associated Instagram account. The Met shows those names for a person to choose and keeps the exact `pagina_id`. It does not guess from the brand name: the WhatsApp campaign builder rejects the request when this identifier is missing.

  3. 3

    Build the WhatsApp package and leave it paused

    With the account and Page resolved, the Met collects the internal name, daily budget in the account currency, copy, headline, public image URL and targeting. It also asks whether housing, employment, credit, financial products, politics or social issues require a special category. The tool creates the campaign, ad set, creative and ad, wires the destination to the workspace number and returns all four identifiers. Everything remains paused. A private image, local file, or JPG or PNG larger than 8 MB is rejected before the creative is built.

  4. 4

    Review the setup before putting money in motion

    The Met uses the returned identifiers to read the status and setup again, and compares the account, objective, budget, destination and targeting with what the person requested. The review happens while everything is still paused. If the previous call failed after creating one part, the error lists the identifiers left behind; because there is no rollback or deletion tool, those pieces are removed in Ads Manager before trying again.

  5. 5

    Ask for a final yes with the daily budget in view

    Creating does not authorize activating. The Met repeats the account, Page, WhatsApp number and how much can be spent each day, then waits for an explicit affirmative answer at that moment. Only then does it call the activation tool on the correct identifier. That call is what changes the status to active and starts spending real money. "Leave it ready" or the initial request to create it do not replace this separate confirmation.

  6. 6

    Read conversations without calling them sales

    Once the campaign has delivered, the Met reads performance for the agreed window and can break it down by day, ad set or ad. It returns spend, impressions, clicks, reach, cost per result and conversations started. That last number is how many chats Meta reported, not how many purchases were paid. A newly created or still-paused campaign can return no rows, and the tool marks that as expected rather than inventing performance.

  7. 7

    Pause the exact object that needs to stop

    If the person decides to stop the ads, the Met pauses the campaign, ad set or ad by its identifier. The tool changes the status to paused and the action is reversible, but it does not delete anything or refund what has already been spent. The Met does not decide the cut based on sales because it lacks that attribution: it presents the available data and carries out the pause the person confirms.

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

Not during creation: the campaign, ad set and ad start paused. Spending requires a separate call to `activar`. In this recipe the Met shows the daily budget again and waits for an explicit yes immediately before making that call; asking for the campaign at the beginning does not count as final confirmation.

Because the Page is the identity that signs the ad in Meta. The number resolves where the click lands, but it does not replace the Page. The tool requires both: the `pagina_id` chosen from the listing and a number connected to the workspace.

The tool tries to download it without a session. If the link does not respond, returns a different file type or weighs more than 8 MB, creation fails with that reason. Publish a JPG or PNG reachable over HTTP or HTTPS and try again.

This skill does not know. It can show spend, impressions, clicks, reach, cost per result and conversations started. A chat can end in a purchase, a question or abandonment; following it through payment requires measurement this connector does not send to Meta.

The special category is declared at creation and cannot be changed later. Meta restricts age, gender, interests and other targeting controls for those ads. The Met asks first because omitting the category can make Meta reject the ad, while declaring it incorrectly means rebuilding the campaign.

Keep going

Other automations built on the same tools

Want this automation running on your own data?

We will show it to you with your accounts connected, not with a canned demo.