Overview
This article is for Triple Whale users migrating from Moby 1 Agents to Moby 2 Automations. Its purpose is to provide a side-by-side comparison of features and capabilities to help you understand how your existing Agents map to the new Automations framework. For conceptual details, see Moby 2 Automations. For migration steps, see How to convert your Agents to Moby 2 Automations.
Feature comparison
Capability | Agents (Moby 1) | Automations (Moby 2) |
AI engine | Moby 1 | Moby 2 |
Scheduling | Preset cadence options | Minutes, hours, days, or weeks, plus on-demand runs |
On-demand run (outside the schedule) | Limited | Yes |
Report format | Plain text / terminal-style | Formatted HTML report, shareable |
Slack delivery | Available; reconnect required when integrations expire | Yes, with built-in reconnect prompts when integrations expire |
Email delivery | Limited | Yes |
Google Sheets output | Available | Yes, with reconnect flow |
In-app delivery | Yes | Yes |
Multi-store support | Limited | Improved, prompts confirm the target store on build |
Prompt language | Natural-language (Moby 1) | Natural-language (Moby 2), same syntax, stronger results |
Copying an old prompt over | n/a | Supported, paste directly. Moby flags anything that won't map cleanly. |
Credit usage | Draws from monthly credits per run | Draws from monthly credits per run (same model) |
Integration access | Triple Whale data | Triple Whale data + deeper integration reads |
Actively developed | No, frozen | Yes, new features ship here |
Chat history | Moby 1 chat history lives under Settings → Moby Tools → Chat History (Moby 1) after you enable Moby 2. Not surfaced in Moby 2 Threads. | New Threads view. Moby 1 and Moby 2 conversations are kept in separate places, they do not merge. |
Sunset | Being sunset, date to be announced | Generally available; no sunset |
Gaps: what automations don't do (yet)
A small number of Agent patterns don't have a direct Automations equivalent today. If any of these describe an Agent you rely on, open a support chat before sunset so we can plan a workaround.
Agent pattern | Automation status | Recommended path |
Action Agents (updating ad budgets, changing bids, pausing campaigns) | Standard Automations don't execute changes in ad platforms today, they surface insights and reports. | Open a support chat before sunset so we can scope the right path for you. |
Pass/fail branching (conditional logic on a metric threshold) | Not yet supported | Either flatten the logic into a single analysis prompt, or open a support chat. |
File dependencies (reading an uploaded COGs sheet or similar) | Different setup required | Open a support chat, file handling in Automations uses a different flow. |
For the typical reporting, analysis, and recap use cases, none of the gaps above apply, the prompt copies over directly.
Related questions
Can I copy my Agent prompt directly into an Automation?
Will the output look the same as my Agent was producing?
Do Automations cost more credits than Agents?
Do action agents work in Automations?
What if my Agent depends on an uploaded file?
Do Automations support pass/fail branching?