Skip to main content
A Run doesn’t have to be started by hand. The CLI lets you set up three ways for an Agent to start work on its own: on a recurring schedule, when an external event fires, or when a new Case lands on a Queue.

Schedules

A schedule fires against an Agent’s live Setup on a recurring cadence — daily, on workdays, weekly, monthly, or a custom cron expression.

Create a schedule

Update or delete a schedule

update also accepts --timezone, --day, --day-of-month, --cron, and matching --clear-* flags to remove a field. Run duvo agents schedules update --help for the full set.

Case triggers

A Case Trigger connects an Agent to a Queue so it automatically picks up new Cases as they arrive. For background on the Queue system, see Queue.
Only the person who set up a trigger or a team Builder or admin can disable it or change its queue. Disabled triggers stay attached to the Agent but stop dispatching new Runs until re-enabled.
--concurrency only accepts 1 (run Cases one at a time). Use --clear-concurrency to fall back to the platform default, which runs Cases in parallel. Raising a Queue’s parallel limit above the platform default is configured by Duvo and can’t be set from the CLI or API.

Event triggers

An event trigger starts a Run automatically when an external event fires — an email arrives, a Linear issue is created, a file changes in Google Drive, and so on. The Connection must already be set up for the Agent before you can add a trigger for it.
Each Connection has at most one event trigger per Agent, so set creates the trigger the first time and updates it after that. Use triggers types to discover the --integration and --trigger-type values a Connection supports.

Managing Agents

Create and configure the Agents these triggers and schedules fire

Starting Runs

Start and monitor Runs by hand

Cases and Queues

Inspect the Cases a Case Trigger picks up