Missions and triggers

Give a bot recurring routines, one-off actions and event triggers, and follow what it does from its reports and monitoring.

A bot can work without you: on a schedule, when something happens, or on a task you queue. Set it up from the bot's menu.

The bot menu

Open it in any of three ways: right-click the bot in the sidebar, right-click the top of its chat, or click … at the top right of the chat (or on the bot's line in the sidebar). It's the same menu everywhere:

  • Edit profile: name, role, instructions, color and notifications.
  • Settings: every section below, in a submenu.
  • Share this bot, for a bot on Neoo Cloud.
  • Pin, Mark as unread or Mark as read, Mute notifications, and Move to section (an existing section, No section, or New section…).
  • Duplicate, Copy conversation ID, Hide from sidebar, and Delete (click Confirm to delete).
Settings sectionWhat you find there
AutonomyCapabilities, actions, event triggers, decisions and activity.
MemoryDurable memory and the working brief.
SkillsProcedures the bot learned.
RoutinesScheduled work and reports.
WorksThe bot's works, with archive, mute and delete.
DataThe bot's private tables.
IntegrationsAccount, plugins and MCP, Neoo Vault, browser and Computer Use.
ChannelsTelegram, Slack and WhatsApp.
MonitoringRuns, failures, tokens and cost.
Advanced settingsModel, background activity, export, archive and deletion.

A section opens in a panel on the right of the chat. Click the section name at the top of the panel to switch to another section without reopening the menu. Clicking the bot's avatar or name at the top of its chat opens Edit profile directly.

Routines

A routine runs a mission on a schedule.

  1. Open Settings → Routines and click New routine.
  2. Give it a Name and describe its Mission.
  3. Choose a Schedule type:
    • Interval: every few minutes.
    • Cron: at fixed times. For example, 0 9 * * 1-5 runs Monday to Friday at 9:00.
    • One time: once, at a date you choose.
    • Heartbeat: a regular check that stays quiet when there is nothing to report.
  4. Click Create automation.

Each routine has Run to start it now, Pause routine and Resume routine. A bot can have up to 50 routines.

In the routine form, After being offline decides what happens to runs missed while Neoo was closed. Advanced settings adds retries, Quiet hours and Notifications.

Follow a routine while it runs

While a routine runs, it has a row in the dock above the bot's message box, with Routine running. Click Open to follow the run's conversation in the same place, live. Click Back to chat to return.

If the routine asks you something, the row says Routine waiting for your answer. Open it and answer there: the run waits until you do.

A routine uses the same browser as the bot, with the same sign-ins. To watch it move from page to page, click the globe button (Session browser) at the top of the chat. The chat and a routine share this browser, so avoid asking the bot to browse while a routine is using it.

React to new events with a watcher

A routine can also wait for new items in any source (suggestions, tickets, emails, rows of a sheet) and handle each new item in its own run (listed with the bot's works).

  1. In the routine form, under Trigger, choose On new events (watcher).
  2. Write the Watcher script (Node.js), or ask the bot to write it. The script runs on the routine's schedule, without AI and without using tokens.
  3. Choose what happens to Items already there on the first check: ignore them and react only to new ones, or start a run for each.
  4. Set Threads at once to the number of items the bot may handle in parallel (1 to 5).
  5. Click Test watcher to run the script once. It lists the events it found without starting any run.

Each item never seen before starts a run, listed with the bot's works and titled after the item, with its content in the first message. You can open it and reply there like in any work. The schedule only decides how often the source is checked: use an interval of at least 15 seconds, or cron.

The script reads what the previous check saved on its standard input, and prints one JSON line per item:

let raw = "";
for await (const chunk of process.stdin) raw += chunk;
const { state } = JSON.parse(raw); // saved by the previous check
const response = await fetch("https://api.example.com/suggestions", {
  headers: { Authorization: `Bearer ${process.env.API_TOKEN}` },
});
for (const item of await response.json()) {
  console.log(JSON.stringify({ event: { id: String(item.id), title: item.title, payload: item } }));
}
console.log(JSON.stringify({ state: { checkedAt: Date.now() } }));

Each event needs an id. Add a fingerprint (for example a modification date) to react again when the same item changes. {"log": "..."} lines appear in the test result, and {"error": "..."} marks the check as failed.

For secrets, add lines such as API_TOKEN=vato://Personal/my-api/token to Variables. Neoo reads the value from the Neoo Vault when the script starts and hides it from the logs. The vault item must allow the node command.

After 5 failed checks in a row, the routine pauses and you get a report. The routine card shows the last check and how many new items it found.

Actions

An action is a one-off task the bot works on by itself.

  1. Open Settings → Autonomy, then the Actions tab.
  2. Click New action.
  3. Fill in a Title and the Expected outcome. Steps, checks, a due date and dependencies are optional.
  4. Under Automation model, choose the model and account the action runs with.
  5. Click Save, then Queue mission.

By default the bot closes the action when it's done. For a sensitive result, check Wait for my approval before completing this action: the action then waits in Needs review until you click Accept results. Check the evidence the bot lists before you accept.

Event triggers

An event trigger creates an action when something new happens. Open Settings → Autonomy → Routines and events and click New trigger. A trigger can watch:

  • a Project file;
  • a read-only tool of an app you connected through Composio;
  • a Webhook: a public URL that another service calls (see Webhooks).

For files and Composio, the first check only records what already exists. After that, each new item creates one action, without duplicates. Fixed times and intervals are routines, not triggers.

Webhooks

A webhook lets another service start your bot: a payment, a form, a monitoring alert, a GitHub event. Each call to the webhook's URL creates one action, and the content of the call is attached to it.

Create a webhook

  1. Open Settings → Autonomy → Routines and events and click New trigger.
  2. Choose Webhook as the kind and write the action the bot must perform on each call.
  3. Under Accepted methods, keep POST or tick the other methods the sender uses.
  4. Optional: fill Signature header (optional) and HMAC secret (optional) to verify the sender (see Verify the sender).
  5. Click Save. The Webhook URL appears once. Click Copy URL, give it to the sending service, then click I copied it.

The bot can also manage its own webhooks: ask it in the chat, or use the tools gateway_bot_webhook_create, gateway_bot_webhook_list, gateway_bot_webhook_rotate and gateway_bot_webhook_delete. Deleting needs your agreement, and these tools are not available in Plan mode.

What the sender must do

Call https://api.vatoide.com/api/bots/hooks/<id>/<secret> (the URL you copied).

AnswerMeaning
202 with {"accepted":true,"eventId":"…"}The call was accepted and queued for your bot.
404The webhook doesn't exist or the secret in the URL is wrong. Both cases look identical on purpose.
405The method isn't in Accepted methods. The Allow header lists the accepted ones.
410The webhook is disabled.
413The body is larger than 256 KiB.
429Too many calls; retry after the delay in Retry-After.

HEAD and OPTIONS calls never start anything, and neither do the link-preview robots of chat tools (Slack, Discord, Telegram, WhatsApp, LinkedIn, Facebook, X). Pasting the URL in a chat is safe from that side, but remember that the URL is a secret.

Only the body, its Content-Type and the signature header you chose reach the bot. Other headers, cookies and query strings from the caller are discarded.

What the bot receives

The action starts with your instruction, followed by the content of the call. The content is clearly marked as untrusted external content: the bot reads it as information and is told never to follow instructions found in it, even if the sender wrote some. JSON is pretty-printed. Only the first 10 KB of text are given to the bot; larger bodies are cut and the action says so. Binary content is summarized, not shown.

Verify the sender

Set a Signature header (optional) (for example X-Hub-Signature-256, Stripe-Signature or X-Neoo-Signature) and an HMAC secret (optional) shared with the sender. The bot then checks the HMAC-SHA256 signature of the exact body before doing anything:

  • sha256=<hex> or plain hex, as GitHub and most services send it;
  • the base64 form, as Shopify sends it;
  • Stripe's t=…,v1=… form, which also rejects calls older than five minutes.

A call without a valid signature is dropped and starts no action. Without a secret, every call is accepted, so keep the URL private. The secret is stored only in the keychain of the computer that runs the bot (or, for a bot on Neoo Cloud, on its Neoo Cloud machine). It is never sent to the Neoo servers and never appears in the chat: you type it in this panel, not in a message.

When your computer is off

Calls received while the computer is off are kept for 7 days and delivered when Neoo reconnects. Each call is delivered once: if it arrives twice, the action is created once. A bot on Neoo Cloud receives its calls on its Neoo Cloud machine, so they don't depend on your computer.

The webhook card

Each webhook trigger shows its accepted methods, Last call (or Never called) and the number of calls. Rotate URL replaces the URL, Send a test sends a test call to the bot, and Disable / Enable stops or resumes it; a disabled webhook answers 410. A test call isn't signed, so it works even when an HMAC secret is set.

What the Neoo server sees

Neoo normally never sees your prompts or conversations. A webhook is the exception for the data others send you: the Neoo server receives the calls made to the URL (body, method, content type and signature) because it is the public address. It keeps the content only until your bot has taken the call, and for 7 days at most; after that it keeps nothing but the time, method and size of the call, which the app doesn't display. Your instruction, the bot's work and its answers stay end-to-end encrypted. Don't have a service send data you don't want Neoo's server to see; send a reference and let the bot fetch the details itself.

Reports

Results of routines and actions arrive in the bot's chat as report cards, with a notification. In Settings → Routines, under Reports, choose After each run, or Daily digest at a time of your choice to group successful runs into one message a day.

Failures are always reported right away. In a routine's Advanced settings, Only report what changed keeps the bot silent when there is nothing new.

When a run fails or gets blocked, the bot comes back to you in its chat with a question, for example to reconnect an account.

Each routine and each event trigger keeps a working ledger shared by all its runs, even when durable memory is off. The bot writes there what the next run needs: when it last checked, which incidents it already reported, and where it sent notifications. A routine's ledger belongs to that routine only; it is not shown in the chat.

Memory

Settings → Memory holds two things:

  • Durable memory: decisions, preferences and facts loaded into every turn. You can edit it directly.
  • Bot working brief: what the bot learned about its mission during your conversations. Correct it by telling the bot in the chat.

Monitoring

Settings → Monitoring shows runs, failures, tokens and cost over a period you choose, with a chart of Runs per day and the Recent failures.

Next step

Choose where your bot runs