Moby Automations: reporting, approvals and run checks

Moby Automations can turn a recurring performance question into a scheduled report. Before allowing the same workflow to change an advertising account, check its approval settings and the exact actions it can take.

This guide covers Triple Whale’s documented Automations workflow as checked on 18 October 2026. It is not a new launch announcement or a test of campaign performance.

Start with a report you can check

Triple Whale’s setup guide requires a Moby account and the relevant connected integrations. Action access is additionally required for workflows that propose or make account changes. Describe the recurring job in chat, including the schedule, timezone and destination. The schedule uses the timezone specified for the automation, rather than your laptop clock.

Moby creates an initial kickoff run for review. Check the figures, comparison period and delivery before relying on the recurring schedule. Confirm that the automation appears in its list and that the first scheduled run follows the intended timing.

Our suggested first task is a report only: yesterday’s spend and attributed revenue for a named account, compared with the preceding completed day. Specify the currency and attribution definition, ask it to identify missing data, and explicitly exclude account changes. Compare that first result with the underlying reporting before expanding the task.

Separate reporting from permission to act

The Automations overview distinguishes information reports from workflows that prepare or execute supported changes. Execution follows the account’s approval behaviour; a scheduled run does not necessarily stop for human review.

Under the action review procedure, an action requiring approval presents a card with its reason and details. Inspect the platform, affected entity, proposed value and previous value where available. You can approve, reject or ask for a revised proposal.

For an initial trial, we recommend requiring review and naming the campaigns the workflow must exclude. Write down the allowed changes and assign a reviewer. After an important action, inspect the connected platform as well as Moby’s result. Keep the Actions log for the decision record; do not assume every change can be reversed automatically.

A completed run is not the same as delivered work

Triple Whale’s troubleshooting guide separates scheduling, delivery and action failures. If nothing runs, inspect status, timezone and account usage limits. If output exists in the conversation but never arrives, check the destination: for Slack, the app must belong to the channel; for email, inspect recipients and spam.

If a run produces no account change, inspect pending approvals and the Actions log. A rule may simply not have matched. Check the recorded outcome before changing instructions or requesting another attempt.

For a related campaign preparation workflow, see our Ads Uploader MCP review guide. In either case, choose a specific job and verify its output before expanding what the tool can do.