Building and editing playbooks with Aero

Updated

Aero can draft a new playbook from a description, and it can change a playbook you have open in the playbook editor. You describe what you want in plain language, and Aero builds or edits the modules, tasks and subtasks for you.

This feature is available when it's turned on for your organization. If you don't see it, contact your OnRamp team.

When to use it

  • Starting a new playbook. Describe the playbook you need, or attach an outline, SOW, kickoff deck or process doc, and Aero builds a first draft.

  • Changing an existing playbook. Ask Aero to add, rename, move or update parts of a playbook draft instead of making each change by hand.

  • Building a task's form. Describe the form a task needs, and Aero drafts its subtasks.

How it works

Ask Aero

Ask Aero is available when Aero is turned on for your organization and you have access to it. When it's available, an Ask Aero button appears in the header of pages that support it, such as the playbook editor. Select it to open the Aero chat.

Create a playbook from a description

  1. Go to Library > Playbooks.

  2. Select Create Playbook.

  3. In Create New Playbook, select Describe It.

  4. Under What kind of playbook do you need?, enter your description.

  5. Optional: Under Attach a file, add one file to build from.

  6. Select Generate Playbook.

The new playbook opens as a draft in the playbook editor. The Aero chat opens with your prompt already in it, and Aero builds the playbook there.

Create Playbook appears only for people who can create playbooks. Describe It (marked Recommended) appears only when Ask Aero is available to you. Without it, the dialog offers only Start Blank, and it opens only when you can create playbooks in more than one workspace. Otherwise, selecting Create Playbook creates a blank playbook right away.

Edit a playbook with Aero

To edit a playbook, open it in the playbook editor, select Ask Aero, and tell Aero what to change. Aero applies changes while you're editing the playbook's draft. It doesn't apply changes while the playbook is read-only.

Your edits, and Aero's, go into the draft. When you select Publish, the draft replaces the current published version, and new projects use it. Projects that are already running change only if you choose to update them when you publish. That choice appears when the playbook already has a published version and updating active projects is turned on for your organization. Saving doesn't create a new version.

What Aero can change

At the playbook level, Aero can:

  • Rename the playbook and update its description.

  • Change playbook settings. A setting your organization can't use isn't applied.

  • Attach data fields to the playbook.

For modules, Aero can:

  • Add modules and rename them.

  • Move tasks between modules to change how content is grouped.

  • Add modules from the Library.

For tasks, Aero can:

  • Add tasks with descriptions.

  • Set due dates and date rules.

  • Make a task internal or customer-facing, or make it a review task.

  • Set dependencies between tasks.

  • Create task roles and assign them to tasks.

For subtasks, Aero can add subtasks to tasks and update existing ones.

Build subtasks in the task builder

In the task builder, a task with no subtasks yet can show a Build with Aero card, tagged NEW. The card shows when Aero's task builder is also turned on for your organization. The task must be in a playbook draft you're editing, or be a library task or module task you can edit. Project tasks never show the card. Describe the form you need there, and Aero drafts the task's subtasks.

Attach files

Aero can use a file as the foundation for a playbook or as context for your description.

  • Create New Playbook takes one file, under 5 MB. The Attach a file field appears after you select Describe It, and Describe It shows only when Aero is available. A file over 5 MB isn't attached, and no error message appears.

  • The Aero chat takes up to 5 files per message. Each file must be under 5 MB, and all the files in one message together must be under 5 MB.

The chat lets you attach any file type except executables and scripts, such as EXE, MSI, DLL, BAT, PS1, SH, JAR, APK and DMG files. Aero can read only Excel (.xlsx), CSV, Word (.docx), PowerPoint (.pptx), PDF, plain text (.txt, .md) and images (.png, .jpg, .gif, .webp). If you attach another type, such as an email or an archive, Aero tells you it can't read that file type and lists the types it can read. If you attach an executable or script, the chat shows Executable files can't be attached: followed by the file names.

Limits

  • Aero only changes a playbook while its draft is open for editing in the playbook editor.

  • Aero's changes stay in the draft until you publish it.

  • The Build with Aero card shows only on a task that has no subtasks yet, and never on a project task.

  • File size and count limits apply, as listed in the section on attaching files.

More in OnRamp Aero