Lesson 2 of 10 · 5 min
Your first workflow from a template
Create a workflow from a template, connect the accounts its nodes need, and run it once as a test.
Video walkthrough coming soon
Autopilot
Start from a template
A template is a finished workflow you copy into your project and adjust. It is the fastest way to see how the pieces fit. When you create a workflow in Autopilot, pick a template instead of a blank canvas.
The templates you can start from today:
- Post my library on a schedule. Every weekday morning, it takes the next creative from your library, writes a caption, and schedules it on a connected channel.
- Generate and schedule weekly ads. Each Monday, it generates a fresh batch of static ads, waits for them to render, and puts them on the calendar for the week.
- New creative ready to Slack. When a creative finishes rendering, it posts it to a Slack channel.
- Winner detected to new ad set. When an ad beats its benchmark, it asks for approval and launches it in a new ad set.
- Weekly performance digest. Every Monday, it pulls last week's ad performance, summarizes it with AI, and sends it to Slack.
- Webhook to static ads. Send a product brief to a webhook and get static ads generated for it.
- Approve then publish. It generates an image, gets a teammate's approval, then publishes it to a channel.
- Brand chat assistant. A members-only chat that answers with an AI agent that can search the web.
Fill in what it needs
A template is a starting point, not a finished job. After you pick one, check each node that shows a warning. The most common gap is a missing connection. A node that posts to Instagram needs a connected Instagram account, and a node that posts to Slack needs Slack. Pick the account in the node, or connect it from Integrations.
Then read the trigger. A schedule template may say Monday at 9am. Change it to the day and time you want. The workflow uses your project's timezone unless you change it in workflow settings.
Run it once
Click Execute workflow at the bottom of the canvas. The draft runs now. Each node shows a spinner while it works, then a tick and an item count when it is done. Open any node to see what it produced.
A test run is a real run. If the workflow posts or sends something, the test posts or sends it too. Before you test, switch off any node you do not want to fire, or pin sample data on it. Lesson five shows how.
Leave it as a draft until it works
A template you have only tested is still a draft, so nothing runs on its own yet. When the output looks right, you publish it. That is lesson six.