Routines

Create a routine

Only the project owner can create, edit or enable a routine. Open Routines, choose an owned project and write the instruction Numo should receive. Mention relevant issues, pages or objectives. Each occurrence has a private Numo conversation, history and Minddy tools. Routines organize and track work, for example a weekly triage, a review of stale issues or a weekly summary; they do not change repository code.

Choose Scheduled or Event. Database arrivals are an option in the event list.

• Scheduled: choose daily, weekly or monthly, the time and your timezone. Check the first-run preview.
• Event: choose issue creation, entry into a target status, assignment, a comment on a followed issue, feedback receipt, or a new database entry. Choose the target status, person or followed issue where requested. A status trigger includes issues created directly in that status. Assignment requires an actual change of assignee. A comment written by a reader does not start a comment routine.

For a database arrival, choose New database entry in the event list, then a page database in this project. A creation, duplicate, database import or move into that database counts as an arrival. Restoring an entry does not create a new arrival.

Conditions are optional: without them, every matching event can start the routine. Set the delay separately under Start timing. The small information buttons explain waiting behavior and timing. Pickers use the same status, priority, category and person indicators as the rest of Minddy. Use arrow keys and Enter; longer lists include search.

Set the delay after an event if needed, from 0 to 120 minutes. Keep your timezone for Numo's context. Event and database routines listen for future arrivals and have no next scheduled date. Automatic processing requires the instance scheduler; a manual run remains available.

Build conditions that can wait

Use Add condition to build one group of up to 16 conditions. Choose All conditions (AND) or Any condition (OR) for the whole group. Select issue status, assignee, category, priority or effort; for a database, select its typed property. Choose a compatible operator and value. People, categories and databases must belong to this project. Nested groups cannot be added. Saved nested rules keep their meaning; if they cannot be shown as one equivalent group, Replace conditions clears them so you can build a new group.

For example: entry into Triage, with all conditions requiring category Backend and priority High. An issue arriving without a category stays waiting. Adding Backend later can start the occurrence. Once consumed, that waiting item cannot start a second occurrence. Leaving the target status cancels it; entering again creates a new waiting item. A reassignment similarly replaces its waiting item.

An entry created without its required property stays waiting until an edit satisfies the filter. Removing a referenced property or changing its type shows a filter error: correct the routine's conditions before continuing. The delay is also respected when a filter becomes true. Feedback receipt includes private and pending feedback; running Numo does not publish it or bypass moderation.

Local demonstration of the actual trigger editor. No routine was saved or executed.

Manage and verify runs

Open the routine to inspect waiting conditions, change its instruction or trigger, pause it, or review occurrences. Pausing, deleting or changing its configuration invalidates waiting items. Re-enabling listens to future events without replaying old arrivals. A manual run can start any trigger type without waiting for its event and also consumes usage.

Right-click a routine in the list to open its latest run without selecting it first; Open latest run stays unavailable until the routine has run. The project owner can also choose Run now, Pause or Resume, Edit or Move to trash from the same menu. Resume is unavailable when the instance cannot schedule routines. Other members only see entries that leave the routine unchanged. To create a routine, right-click Routines in the sidebar and choose New routine.

Each occurrence uses the owner's AI budget with a 15% monthly-budget cap by default, including every Numo call of that occurrence. Open its conversation to inspect the source, outcome and questions. When owner input is required, answer in that same conversation; the remaining occurrence budget is retained. Inspect saved results before adjusting a cap or retrying. When ownership is transferred, the former owner's routines in the project are paused and cannot start new work; the new owner creates the routines that should continue.

The cap applies when an included monthly budget is available; an uncapped personal-key mode does not acquire an artificial monthly allowance.

Project automations from earlier versions no longer run and are not converted into routines. Read the transition guide to recreate a workflow as a routine.