Skip to main content
An automation is one of AutoGrowth’s own built-in routines. It runs on a phone in your fleet: the phone opens the real app and drives it like a person would — taps, scrolls, typing. Nothing goes through a social platform’s API, and nothing runs while the Companion on your Mac is closed. There are twenty of them, and the list is fixed. You choose one, fill in its inputs, pick a phone or an account, and say when. One of those runs is called an execution, and you watch it on the Schedule screen. A workflow is a set of automations that repeats every day.

​
Everything here needs Autogrowth MAX

Running an automation — one now, one scheduled, a hundred in bulk, or a daily workflow — requires the Autogrowth MAX licence. Without it, the server answers:
Autogrowth MAX is required to run automations.
MAX is a one-time, invite-only lifetime licence, paid for from your organization’s credit balance. There is no monthly automation plan and no trial. If MAX has not been offered to your organization, buying it is refused with “Autogrowth MAX is invite-only. Contact us for access.” See Credits and billing. One automation costs more on top. Create Account needs the create-account add-on, a separate one-time purchase for the whole organization:
The Create Account add-on is required to run this automation.
There is no way around that one — not even for staff. It is unlocked by payment only.
Automations reach iPhones only. GrapheneOS phones can be watched and driven by hand, but they cannot run automations or scheduled work at all. See Android phones.

​
The catalogue

Names repeat across platforms — there are four different Log in automations and three different Post automations — so always read the platform column with the name. The last column says whether an automation can be a step in a workflow. The ones that cannot are one-off setup jobs: a daily routine fans out across every account on the phone, and logging in twelve accounts every morning makes no sense.

​
Instagram

Confirm login is queued for you automatically after a successful Instagram Log in — you do not normally schedule it yourself.

​
TikTok

​
X

​
Threads

Media inputs are pulled from your content library, never uploaded into the automation itself. Container inputs point at a container that already exists on the phone, except in Create Account, which can also provision a fresh one.

​
Two switches on every run

Both sit on the run itself, not on the automation, so you set them each time you schedule something. AI recovery uses your own Claude API key, set in Settings under Claude API Key. Without one the run reports “Claude API key not configured. Please set it in Settings.”

​
When a log-in fails

The five session automations — the Instagram, X and Threads Log in jobs, Add account and Confirm login — are the ones that decide whether an account is usable. If one of them fails outright, the account is marked Error on the Accounts page instead of the healthy Warming. A later success clears it.

​
Scripts

You will see Scripts in the navigation, a Scripts tab beside Automations whenever you schedule something, and a Create/edit/run scripts permission in roles. A script is a routine you would build yourself in the Script Builder, block by block, instead of choosing one from the catalogue above. It is not available. The Script Builder is locked for every organization — the nav badge reads Soon, the create button is disabled, and the server answers “The Script Builder is coming soon and is not available yet.” It cannot be bought either. Everything a phone does today is one of the twenty automations.

Scheduling

Run one now, schedule one for later, or fill a whole week in one go.

Workflows

Turn a set of automations into a daily routine for a phone.

Content library

Where the media in a posting automation comes from.

Credits and billing

MAX, the create-account add-on, and how credits work.