Set up an Autopilot task

You set up every Autopilot task in the Clevera chat. Say what should happen and when, or pick a recipe, and Clevera opens a setup card already filled in from what it knows. You check the card, click Continue, read the summary and click Create task. Nothing is made and no credits are used until you approve a plan.

There is no separate setup page or wizard. Every way in (the box on Autopilot home, New task, a recipe card, a suggestion's Plan it) opens the chat panel with a setup card.

Before you start#

• Autopilot must be on for your workspace. It comes with the Pro, Business and Custom plans, by invitation. See Get access to Autopilot.
• Your role must be able to create content. Owners, Administrators and Content Creators can set tasks up. Editors can see every task and what it made, but can't set one up: New task is turned off for them, with the reason as a tooltip. See who can do what.
• Some recipes need something first. The article recipes and Keep my help center up to date when we ship need a help center. Recordings need your app's address and, for anything behind a login, an app sign-in. Each release needs a connected repository.
• Add your brand. Tasks use your workspace's brand for every site, video and article they make. The Get started checklist on Autopilot home links to it.

Ways to start#

A recipe card your role can't start stays on the page, greyed out, with the reason when you point at it. New task shows the first six recipes and 7 more to show the rest (Fewer folds them again).

Set up a task#

1. Open the setup card#

   Use any of the ways above. The chat panel opens on the right, titled with the recipe, and Clevera writes "Here’s the setup. Check it and click Continue." The card shows the recipe's name and what it does.

   A short setup is filled in right on the card. A longer one shows a summary of up to four rows, starting with When. A row still missing something reads To fill in.

   

2. Fill in the details#

   On a longer setup, click Fill in the details. Once every required field is filled, the button becomes Edit details next to Continue. The dialog shows every field, section by section, starting with When. Click Close to go back to the card or Continue to check it.

   

   Your edits are kept on the card as you type, so closing the panel or reloading the page doesn't lose them.

3. Click Continue#

   Clevera checks the setup on the spot: your role, every field, and whether the recipe can run that way. A problem shows next to its field, or as a red line on the card. Fix it and click Continue again.

4. Read the summary#

   The card now shows the task's name and a short summary, then a line saying what happens next. Click Back to change something.

   

5. Click Create task#

   The card shows Task created and Open the task, and Clevera writes "Done: the task is set up. Clevera posts here when it needs you."

   

What happens after Create task#

The chat you set the task up in belongs to that task from now on: when its plan is ready, it fails or it needs you, Clevera posts there. If that chat was already about something else, the task gets a chat of its own and the card says "It has its own chat: updates on this task are posted there."

Then you review the plan on the task page: untick what you don't want and click Run. See Understand Autopilot.

The summary after Continue#

The line under it says "Clevera plans it now (free, a few minutes) and posts here when the plan is ready for your review." for a one-off, or "Nothing runs now: Clevera plans a run each time it fires, and you review the plan on the task before anything is made." for everything else.

The recipes#

The recipes appear in the same order on Autopilot home and under New task: first the ones you can start now, then the ones that need a help center, then the ones your role can't start.

Make a help center from a collection is not on Autopilot home: it opens from a collection's Make a help center.

The typical run is a range from past runs, not a quote. Each plan shows the real estimate for every line before you run it, and you are charged for what each line really uses.

The When section#

Every card starts with When. A recipe with one way to run shows it as plain text. A recipe with several shows a Runs switch.

For every option except Once, now and On a schedule, the card notes: "Nothing runs now. Each time it fires, Clevera plans a run and waits for your review before anything is made."

Fields you see on many cards#

Sign-in#

Every recipe that records or explores your app asks how the AI gets in. Clevera never answers this for you.

Add a sign-in… opens Add an app sign-in ("Use a demo or staging account. The AI signs in as it while it records."): the app's address, the login, and two-step verification if your app uses it. The login is encrypted and never shown again after saving, and you confirm with your Clevera password. Only a reference to the sign-in goes into the task: the password never passes through the chat. See Save an app sign-in.

While it records#

Explore recipes call this While it explores. Your own task has a checkbox instead: Let the AI save changes in your app (use a test account). Clevera never ticks it for you.

Your app#

Keep current, Update my videos, the article recipes and Your own task ask whether Clevera may use your app: Use my app (then App address, prefilled with your workspace website, and Sign-in) or Don’t use my app. Without your app, Clevera only updates or writes words; it doesn't record new screens.

Languages#

Content language is the language the task writes in. It defaults to your workspace's. Translations adds more languages, up to 5 in total. Translate new videos into my languages takes 1 to 4 languages.

Fields by recipe#

Approval and budget#

When a task's plan is ready, someone has to approve it, with one exception.

Articles Autopilot writes on your help center always land as drafts that wait for approval: nothing is published for you. Publish for me isn't offered by any recipe.

A schedule also has a Monthly budget in credits (1–100,000). It starts at a suggestion worked out from how often it runs and how many articles it writes each time, for example 300 credits for 5 articles every week. Only a workspace owner or admin can set a budget above the suggestion. See Set a Repeat schedule and monthly budget and Choose how much Autopilot can do on its own.

What setup costs#

What Autopilot can't set up yet#

When you ask for something no recipe or trigger covers, Clevera says so in one sentence, offers the nearest thing that works and passes your request on to the product team. Today that includes:

• Posting or sending anything: Slack, Notion, YouTube, social networks or e-mail. Everything a task makes already shows to the team in a team-wide collection, so there is no "share" step.
• Social clip tasks and blog-post tasks. These are on hold for now.
• Making or exploring new videos on a schedule. Recording and exploring run once, or on each release (Record a video for every new feature).
• Running every hour, or once on a set date.
• Your own task editing or cutting existing videos. Use Update my videos when the product changes or Edit a batch of videos at once.
• Other triggers, such as a new ticket in a support tool.

If a task that already does the job exists (the same recipe, help center or videos, and the same kind of trigger), Clevera shows no new card. It names that task and offers to change it instead. See Change or pause an Autopilot task.

Troubleshooting#

Related#