Overview
This article walks you through building a recurring Automation in Moby chat, from the first description to the kickoff run.
An Automation is a scheduled Moby 2 job. You describe the work once, set the cadence and destination, and Moby runs it on schedule.
Before you begin
You need:
A Triple Whale account with Moby 2
The relevant integrations connected
A clear idea of what the Automation should do
Action access enabled if the Automation will propose or make account changes
If your Automation includes account actions, review Review and approve Moby Actions first.
Steps
Open Moby chat.
Describe the recurring job in plain language.
Include what you want, how often it should run, and where the result should go.
Example:
“Every Monday at 9am ET, send a Meta performance recap for last week to #paid-social, ranked by spend, with ROAS and Cost per Acquisition.”
Answer Moby’s follow-up questions.
Moby may ask for missing details such as cadence, destination, timezone, metric definitions, or how to handle multiple stores.
Name the timezone explicitly.
Schedules follow the timezone you set for the Automation, not your laptop clock.
Confirm the build.
Moby drafts the Automation and runs a kickoff so you can review the output before waiting for the first scheduled run.
Review the kickoff output.
Check the numbers, format, and delivery. If anything is off, tell Moby in the same chat.
Examples:“Shorten this to the top 10 campaigns.”
“Switch the comparison to the previous 30 days.”
“Send this to the growth channel instead.”
Let it run.
Each scheduled run lands in the Automation’s conversation thread, so you can review history and refine instructions over time.
Verify it worked
Check that:
The kickoff output appears in the conversation thread.
The output arrived at the destination, such as Slack or email.
The Automation appears in your Automations list.
The row shows the schedule you set.
The first scheduled run follows the timezone you set.
Tips
Be specific about metrics, thresholds, ranking, comparison windows, and row counts.
Start with a report-only Automation, then add account actions once you trust the output.
If the output should reach someone who does not use Triple Whale, deliver it to Slack or email.
For action Automations, decide who reviews proposed changes and when.
⚠️ Warning: An Automation that includes account actions follows your account’s action approval behavior. Scheduled actions may run automatically or wait for review before execution. When approval is required, Moby prepares the proposed change and waits for approval.
Related questions
How do I create a Moby Automation?
What should I include when asking Moby to create an Automation?
How do I choose an Automation schedule?
How do I send an Automation to Slack or email?
What is a kickoff run?
Can an Automation include account actions?
How do I confirm an Automation was created?