Autopilot is the one place for automation

One place for automation

Autopilot is where automation lives in Pinnora. Open a project and choose Autopilot to see every workflow in that project. You build each one on a canvas, test it, and publish it to make it live. There is no separate Workflows page anymore. Old links to it open Autopilot.

Use Autopilot for anything that repeats or reacts. Post a creative every weekday morning. Make a batch of static ads every Monday. Send a performance digest to Slack. Ask for approval before an ad set goes out. Each of these starts on a trigger and runs again and again until you unpublish it.

Where Atlas fits

Atlas helps in two ways.

It runs one-off long jobs. Ask Atlas to make five ads and schedule them across two weeks, and it runs that as a long job in the background, then stops. That is what the earlier lessons in this chapter cover. Nothing repeats, and nothing is left running.

It drafts Autopilot workflows. Ask Atlas for something recurring, like "every Monday, make five static ads for the spring sale and schedule them on Instagram", and it can draft that as an Autopilot workflow. You open the draft on the canvas, check each node, and test it. Atlas never publishes a workflow or turns on its triggers without your approval. Going live is your decision.

A clean way to choose

• Once, with an end. Ask Atlas for a long job. Schedule this month's creatives, or make these five ads and schedule them.
• Again and again, or on an event. Build it in Autopilot, by hand, from a template, or from an Atlas draft.

A common pattern

Start with a long job in chat to make and schedule a first batch now. If you like the result, ask Atlas to turn the same idea into an Autopilot workflow. Review it, test it with Execute workflow, set a monthly credit budget, and publish it. The Autopilot chapter walks through each of those steps.