Skip to main content
Your automations are working whether or not you’re watching. This recipe brings their results to where you already look: a weekly report for a client, a row in a sheet, a message in your team’s channel. A read key is all it needs, and that’s the key to give a reporting job.

The numbers

Get automation stats counts what one automation did over a window of days, ending now: All four are totals for the automation. Nothing about any individual person comes back.

Every live automation, last 7 days

Each automation costs one stats call, so a large workspace adds up. Pace a big report by the rate limit headers.

Reading them well

  • messages_sent can be higher than times_triggered. One comment can lead to more than one message: an opener and then the link, or a follow-up hours later. Compare messages with messages, and comments with comments.
  • messages_waiting isn’t a fault. Each account sends at a steady pace so Instagram keeps trusting it. When a post takes off, messages queue and drain. Get account health says how long the queue takes to clear.
  • For a failure share, divide failed by failed plus sent. That reads as “of the messages Instagram answered, how many did it refuse”.
  • When messages_failed climbs, ask the account. Get account health lists what Instagram has been refusing and how often, and whether the connection itself needs attention.
  • Triggered but nothing sent? Check the account’s health first. A paused connection sends nothing until it’s reconnected, and automations_that_cannot_fire names any live automation set up so it can never trigger.