Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getnao.io/llms.txt

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

Automations let you schedule headless agent runs on a cron schedule. Each automation stores a natural-language prompt, a schedule, and optional integrations so the agent can deliver results to email, Slack, or GitHub without anyone opening the chat.

​
Creating an automation

  1. Click Automations in the left sidebar.
  2. Click New automation.
  3. Enter a title and the prompt you want the agent to run.
  4. Pick a schedule and configure integrations (see below).
  5. Save.
After creation, each automation gets its own detail page where you can edit settings, review previous runs, and trigger a manual run.

​
Schedule

Every automation runs on a cron schedule. The UI offers presets:
  • Hourly
  • Daily (9 am)
  • Weekdays (9 am)
  • Weekly (Monday 9 am)
  • Monthly (1st at 9 am)
You can also enter a custom cron expression for any other cadence. Use the toggle on the automation detail page to pause or resume the schedule at any time.

​
Run now

Click Run now on the automation detail page to trigger an immediate run outside the schedule. The run follows the same flow as a scheduled execution.

​
Integrations

Each automation can optionally deliver results through one or more integrations. Configure these in the right sidebar of the automation form.

​
Email

When enabled, the agent sends its output by email after the run completes.
  • The automation owner’s email is included by default.
  • Add extra recipients as a comma-separated list.
  • Optionally override the email subject line.

​
Slack

When enabled, the agent posts a message to a Slack channel with its results.
  • Enter the Slack channel ID (e.g. C0123456789).
  • Requires a Slack integration configured in your project settings.
  • The agent resolves @handle mentions to Slack user IDs before posting.

​
GitHub

When enabled, the agent can create issues, open PRs, or post comments on GitHub.
  • Requires a GitHub OAuth connection on the automation owner’s account.
  • Optionally filter to specific repos (comma-separated).

​
MCP servers

When enabled, the agent can call tools from your connected MCP servers during the run. Toggle individual servers on or off per automation.

​
Model selection

By default, automations use your project’s default model. You can override this per automation from the model selector in the form sidebar.

​
Previous runs

The automation detail page shows a list of previous runs with:
  • Timestamp and duration
  • Status badge (running, completed, or failed)
  • Integration result icons showing which deliveries succeeded or failed
  • A link to open the full agent chat for any run
A run is marked failed if the agent did not call an expected integration tool, or if the agent loop itself errored.