Skip to content

Automation · Operations and reporting

Review your clients' sources and spend on WhatsApp on Monday with Whatagraph

Ask on WhatsApp whether any client's source went down and how much they spent: an AI agent checks it in Whatagraph and replies.

How do I check on Monday whether any client source went down and how much they spent?

You write to your Met "did any source go down and how much did each client spend last week?". The Met goes through your clients' spaces in Whatagraph and their data sources, and before telling you one is broken it asks the provider right then whether it still responds. Then it reads the week's spend from each source that responds, tells you which scheduled reports go out this week and, if you ask, exports a report as PDF and gives you the link, which expires in 1 hour. It does not reconnect anything or change how your reports are shared.

What starts it

When someone asks for it

It starts when someone at the agency writes to the Met on Monday, or any day they want, to review the accounts. Each review runs on request; this procedure leaves nothing scheduled.

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

Who runs it

Agency analytics Met with Whatagraph

Social team

This is not a named, seeded Met. It is an internal Met with Whatagraph connected: its work ends when it delivers the status of the sources and each client's spend, or when it tells you which source could not be read and why.

Run by the data analyst Met

Channels: WhatsApp

What you need connected

6 steps · 6 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

    Go through your clients' spaces

    The Met lists the spaces in the Whatagraph team, which are each client's folders, to know whom to review and in what order to reply.

  2. 2

    List the connected sources

    The Met lists the team's data sources, such as each Google Ads account or each GA4 property, with the status they have stored.

  3. 3

    Check on the spot the ones that look broken

    Before telling you a source went down, the Met asks the provider right then whether it still responds, because the stored status can be out of date in either direction.

  4. 4

    Read last week's spend

    For each source that responds, the Met reads last week's spend and gives it to you sorted by client, with the figure as the source returns it.

  5. 5

    Count which reports go out this week

    The Met reviews the scheduled report deliveries and tells you which go out this week, so you know which client will get one with a broken source.

  6. 6

    Export a report as PDF, if you ask

    If you want to review a report before it goes out, the Met exports it as PDF and gives you the download link. It expires in 1 hour and does not change how the report is shared.

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

Because the status Whatagraph stores can be out of date: a source already fixed can still be marked with an error. The Met checks it on the spot before telling you.

This procedure runs on request. A scheduled delivery would be a different automation, with its own trigger.

No. It only reaches the team you chose when authorizing, with the spaces and sources it has.

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.