Skip to main content

Documentation Index

Fetch the complete documentation index at: https://ona.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

This guide covers Automation configuration in detail. For a quick walkthrough, see Create your first Automation.
Automations work best with projects. A project provides the Dev Container configuration, dependencies, and environment settings that your Automation runs against. We recommend setting up a project before creating Automations.

​
Create an Automation

  1. Navigate to Automations in the left panel.
  2. Click New.
  3. Choose Start from scratch or select a pre-configured template.
Automations page

​
Name and description

To set or change the name and description, open the ⋯ menu on the Automation and select Rename. A dialog opens where you can edit both fields.

​
Trigger type

Click the trigger node and then Edit to open the trigger configuration dialog.

​
Runs on

Each trigger includes a Runs on setting that determines where the Automation runs:
ScopeDescription
Projects (recommended)Run on specific projects. The Automation uses each project’s Dev Container configuration and environment settings.
RepositoriesRun on repositories matched by explicit URLs or a search query. Use for large-scale migrations across many repos.
See Manual triggers and Pull request triggers for scope configuration details per trigger type.

​
Guardrails

Control execution limits to prevent Automations from running excessively:
  • Max concurrent actions: simultaneous runs
  • Max total actions: total allowed per run
Maximum values depend on your plan. See Plans and limits for per-plan caps and Guardrails for details.

​
Run Automation as

The Run Automation as selector is at the bottom of the trigger configuration dialog.
OptionWhen to use
Your userManual workflows, personal Automations
Service accountScheduled or shared Automations

​
Steps

Steps execute in sequence within the same environment. Each step can access files, environment variables, and context from previous steps.

​
Step types

TypeUse when
PromptFlexible tasks requiring agent judgment: “analyze and improve”, “update based on context”
CommandDeterministic operations: npm test, docker build
Pull requestSubmit changes for review after making modifications
ReportExtract structured data from the execution: test coverage, dependency counts, build metrics

​
Example workflow

Step 1 (Prompt):    "Upgrade all dependencies to their latest versions"
Step 2 (Command):   npm test
Step 3 (PR):        Create pull request with summary
Guidance:
  • Use prompts for context-aware tasks that vary by repository.
  • Use commands for predictable, repeatable operations.
  • Combine both: commands for validation, prompts for intelligent changes.
Steps configuration

​
Save and edit

Click Save to create the Automation. All settings can be modified after creation.
Pull request triggers require an event source: the GitHub App (for GitHub.com) or a webhook. See Pull request triggers for details.

​
Enable and disable

Disable an Automation to stop it from running without deleting it. Disabled Automations keep their configuration, execution history, and triggers — but no new runs can start (manually or via triggers). To toggle an Automation:
  • From the list: open the three-dot menu on any Automation and select Disable or Enable.
  • From the details page: use the toggle switch next to the Automation name.
Disabled Automations appear with muted styling in the list and show a “Disabled” status label. Use the Enabled / Disabled filter in the status dropdown to find them.
Disabling is useful when you want to pause a scheduled or event-driven Automation temporarily — for example, during a code freeze or while debugging a failing workflow — without losing its configuration.

​
Next steps