Skip to main content
Automations let you run headless agent tasks on a cron schedule, from an external webhook, or when someone leaves feedback in nao. Each automation stores a natural-language prompt, one or more triggers, and optional integrations so the agent can deliver results to email, Slack, or GitHub without anyone opening the chat.

Automations page

Automations in the left sidebar opens a page that lists your automations, with a New automation button. Links back from an automation’s detail page lead there.

Inbox

The Inbox page in the left sidebar (previously Feed) shows your activity and notifications, latest first, including automation runs. Each run entry shows the automation name, run status, timestamp, and links to the resulting chat or story. Use it to follow scheduled runs at a glance without opening individual automations, and Mark all as read to clear it.

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 (up to 40,000 characters) in Agent instructions. In the prompt field, Enter inserts a newline instead of submitting, so you can write multi-line prompts. Save with the save button or Cmd/Ctrl + S.
  4. Add at least one trigger 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.

Edit with chat

The new automation page and every automation detail page have a chat panel next to the form, so you can describe what you want instead of filling every field yourself. Open it with Edit with chat in the page header, or drag the panel edge. The panel can be collapsed and resized. The agent in the panel reads the form as it currently stands, including unsaved edits, and can change it: instructions, triggers, deliveries, and tools. For example: “Run it on weekdays at 8am instead”, “Make the report shorter and easier to scan”, or “Why did the last runs fail?”. Changes made from the chat are applied to the form only. Nothing is saved until you review the form and click save.

Triggers

An automation can be started on a schedule, via a webhook, on feedback, or any combination. Add triggers with Add Trigger in the automation form: On schedule, Via webhook, or nao Events -> Feedback. An automation needs at least one trigger to be active.

Schedule

The schedule trigger runs the automation on a cron cadence. 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.

Webhook trigger

The webhook trigger lets an external system start an automation with an HTTP request instead of (or in addition to) a schedule. Enable Via webhook in the trigger picker; the detail page then shows the endpoint URL and a copyable example curl. Send a POST to the automation’s run endpoint, authenticated with an organization API key (the same nao_... bearer keys used by nao deploy). Open Settings -> Organization Settings, then use the Organization API Keys card:
On success the endpoint starts a run and responds 202 with { runId, automationId, status }. It returns 401 for a missing or invalid key, 404 for an unknown automation or a key from another organization, 403 if the webhook trigger is disabled, and 409 if the automation is paused. Pausing gates every trigger: a paused automation rejects its webhook too. Automations without a schedule stay active until you remove or disable their webhook and feedback triggers.

Feedback trigger

The On feedback trigger starts a run every time someone votes on an answer or a story. Add it from Add Trigger -> nao Events -> Feedback, then choose:
  • Votes: Any vote, Thumbs up, or Thumbs down.
  • Sources: Chats & stories, Chats, or Stories.
The trigger fires on votes from the web chat, from stories, and from the feedback buttons in Slack, Microsoft Teams, Telegram, Discord, and Mattermost. Each vote starts its own run, so voting again on the same answer (for example to add an explanation) starts another run. The run receives the event details in its prompt: the vote, who submitted it, the chat or story title and a link to it, and the explanation if one was given. For chat feedback, it also gets the question and the rated answer. Use this to triage downvotes, open an issue, or post a digest to Slack. Access rules:
  • Chat feedback exposes other users’ conversations, so it only runs automations owned by an admin or context admin. Other owners can only use the Stories source.
  • Story feedback only runs automations whose owner has access to the story.
Existing feedback notifications are unchanged and still sent alongside the automation. Pausing the automation’s schedule also stops its feedback trigger.

Run now

Click Run now on the automation detail page to trigger an immediate run outside any schedule or webhook. 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 one or more Slack channels with its results.
  • Enter channel IDs (e.g. C0123456789) or public channel names (e.g. #sales). Separate several channels with commas, semicolons, or new lines. Each channel becomes its own token that you can click to edit or remove.
  • Malformed entries are highlighted in red with the reason (for example “Add # before channel names, like #general.”). Saving is blocked until they are fixed or removed.
  • Requires a Slack integration configured in your project settings.
  • The agent resolves @handle mentions to Slack user IDs before posting.
To keep the channel uncluttered, the agent posts a short headline to start a thread, then delivers the full report inside that thread. Charts and stories are uploaded into the thread automatically. With several channels, every channel gets the headline and its own thread with the full report. One failing channel does not block the others: the delivery only fails when no channel receives the message.

GitHub

When enabled, the agent gets a set of dedicated GitHub tools:
  • github_read - fetch repository data (issues, PRs, files, branches) for context
  • github_create_issue - open new issues
  • github_create_pull_request - open new pull requests
  • github_add_comment - comment on issues or PRs
Requirements:
  • A GitHub OAuth connection on the automation owner’s account.
  • Optionally filter to specific repos (comma-separated) to scope which repositories the agent can access.

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. The list only shows the MCP servers your user groups grant you, admins included, matching what a run can use.

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 run posted to several Slack channels shows a delivered / total badge, with the result for each channel in its tooltip
  • 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.

Managing all automations (admins)

Admins can review every automation in the project from Settings -> Automations (All automations). The page is only shown when automations are enabled. The table lists automations created by every member, with their Automation, Owner, Status, and Last run. If an owner no longer has access to the project, their row shows a Removed badge (or Deleted if the user no longer exists) and a banner flags it. These automations keep firing, and every run fails, until you transfer, disable, or delete them. Actions per automation:
  • Enable / disable - pauses the schedule, which also blocks the webhook and feedback triggers. For automations without a schedule, disabling switches off the webhook and feedback triggers.
  • Transfer ownership - pick another project member (viewers are excluded). Past run chats move to the new owner.
  • Delete - after confirmation, removes the automation and all its past runs.
For runs, success rate, and failures across all automations, see Automations monitoring.