Moby 2 Automations

Overview

As a Triple Whale user, you can use Moby 2 Automations to handle repetitive tasks. You will save time by letting Moby generate recurring reports, monitor performance thresholds, and prepare account actions according to your approval settings.

Moby 2 Automations are scheduled Moby workflows. Instead of asking Moby for the same report, analysis, or monitoring task every week, you can set it up once and let Moby run it on a schedule.

Automations are useful for recurring work such as:

Weekly performance summaries
Daily campaign monitoring
Slack or email reports
Store health checks
Budget pacing reviews
Ad account rule checks
Follow-up workflows
Action proposals for connected platforms

Each Automation has its own conversation thread. The thread keeps the Automation’s instructions, scheduled runs, outputs, and refinements in one place.

Key terms

Term	Meaning
Automation	A scheduled Moby workflow that runs recurring work.
Run	One execution of an Automation.
Kickoff run	The first run Moby creates so you can review the Automation before waiting for the scheduled time.
Cadence	How often the Automation runs, such as daily, weekly, or monthly.
Destination	Where the Automation sends output, such as a Moby thread, Slack channel, or email.
Action Automation	An Automation that proposes or makes supported changes in connected platforms.
Action approval behavior	How your account handles supported actions, including whether an action can run automatically or must wait for review.

How it works

Moby 2 Automations follow a simple loop:

You describe the recurring job.
1. Tell Moby what to do, how often to do it, and where to send the result.
Moby asks for missing details.
1. Moby may ask about cadence, timezone, destination, filters, metric definitions, or approval expectations.
Moby creates the Automation.
1. Moby turns your instructions into a scheduled workflow.
Moby runs a kickoff.
1. The kickoff lets you review the first output before the Automation runs on its normal schedule.
The Automation runs on schedule.
1. Each scheduled run lands in the Automation’s conversation thread.
You refine it over time.
1. If the output is too long, missing a metric, using the wrong comparison window, or going to the wrong destination, tell Moby what to change in the Automation thread.

Automations and actions

Some Automations only report information. Others can prepare or make supported changes in connected platforms.

For example, an Automation can:

Review ad performance every morning
Identify campaigns that crossed a performance threshold
Prepare budget or status changes
Explain the reason behind each proposed action
Run supported changes or wait for review, depending on your account’s action approval behavior

When a scheduled action requires approval, Moby prepares the proposed change and waits for review before execution. If approval is not required for that action, the action may run automatically according to your account’s action approval behavior.

⚠️ Warning: Actions run in your live connected accounts once executed. Use clear rules, thresholds, and exemptions for any Automation that can affect ads, budgets, products, discounts, audiences, or customer-facing content.

When to use Automations

Use Automations for recurring work that has a clear schedule and repeatable instructions.

Good use cases include:

“Send a weekly Meta performance summary every Monday at 9am ET.”
“Every morning, check campaigns with spend above $500 and ROAS below 1.0.”
“Send a Slack recap of yesterday’s sales, spend, ROAS, and new customer revenue.”
“Monitor campaign pacing and flag anything overspending.”
“Create a weekly executive summary with wins, risks, and recommended next steps.”

Trade-offs and considerations

Automations work best when the task is specific. Before creating one, decide:

What date range should Moby use?
What metrics matter?
What filters should apply?
What thresholds should trigger attention or action?
Where should the output go?
Who should review proposed actions?
What should Moby never change?

If the Automation includes account actions, define guardrails before it runs. For example, you can tell Moby which campaigns to exclude, how much budgets can change, or whether new campaigns should be created in a paused state for review.