A team with one goal: calendar, intervals and result checks

A team workflow and model orchestration solve different problems. A team organises agents and roles around a shared goal; orchestration defines how selected models collaborate within an agent’s work.

Define one result

For example, prepare a weekly product-change review. Specify sources, date range, final document format and constraints. Assign collection to one agent, checking to another, and synthesis to a team lead.

Choose a trigger

Manual launch, a specific date and time, repeating intervals and cron are supported. Intervals start at five minutes. First run the workflow manually on a safe task and review each stage.

Requirements for autonomy

The host computer and NC AgentOS core must be running at the scheduled time. Scheduling does not turn an off-line laptop into a 24-hour server. Server execution needs a checked environment and monitoring. CRM, ERP and other integrations need separate API/MCP access and permissions.

Assign a process owner, spending limits, error handling and human-review boundaries. Discuss your first controlled workflow before making it recurring.