What a workflow is

A job that finishes without you

A workflow is like setting a dishwasher running. You load it, press start, and walk out of the kitchen; it works through the cycle whether you are watching or not. Ask Atlas for a workflow and the same thing happens. You describe a goal, Atlas writes a plan, and that plan runs to completion on its own. It survives the chat turn that kicked it off, a page reload, and the time limit that cuts off any single request. You do not have to sit and wait.

Underneath, the shape never changes: plan, then render if new creatives are needed, then schedule. A finished workflow leaves your creatives posted to a calendar, lined up on the social channels you have connected.

Where it lives

A long job lives in Atlas chat. You start it by asking Atlas, and you check on it by asking Atlas too. There is no separate page for these jobs. The old Workflows page is gone, and its link now opens Autopilot.

Autopilot is a different thing. It is the canvas where you build automations that run again and again. This chapter is about one-off long jobs you start from chat. The last lesson explains how the two fit together.

An honest note on maturity

This is a new feature. Read this chapter as a guide to what it does rather than a tour of something in daily use. The mechanics are real and shipped. The habits around them are still forming.

The clearest way to place it: a workflow is the durable version of asking Atlas to plan a content calendar. Small job, and one chat request is plenty. Large job, or one where renders must finish before anything can be scheduled, and a workflow is the right tool.