Use cases
Routines work best for recurring questions where an AI-written response adds more than a static export would. For example:- Morning briefings for sales teams — “Summarize yesterday’s closed-won deals by rep and flag any account that slipped to next quarter,” delivered before the team logs on
- Operational summaries — “Describe how today’s order volume and fulfillment times compare to the same day last week, and call out anything unusual”
- Pipeline and revenue narratives — “Write a short update on how we’re tracking against this month’s revenue target and which segments are driving the change”
- Plain-language monitoring — “Check for any spikes in error rates or refunds over the last 24 hours and explain what you find”
How routines work
A routine runs your prompt through the Omni Agent on the schedule you set. Each run executes independently and respects your organization’s permissions and data access controls. Today, the result is delivered as text by email to the recipients you specify.Creating a routine
Open Routines from the sidebar in your Omni instance to view, create, edit, and delete your routines. You can also manage routines programmatically through the API. When creating a routine, you define:- Name — A descriptive name for the routine
- Description — Optional details about what the routine does
- Prompt — The instruction the Omni Agent runs on each execution
- Model — The data model the routine queries, with an optional topic to focus query generation
- Schedule — When and how often the routine runs, set with a cron expression and a timezone
- Recipients — The users who receive the result by email
Managing routines
From the Routines page, you can:- View your routines and whether each is active or paused
- See when each routine last ran and when it will run next
- Edit a routine’s settings, prompt, schedule, or recipients
- Pause or resume a routine
- Delete routines you no longer need
Programmatic access
In addition to the UI, you can create and manage routines programmatically using the AI Routines REST API. The API provides five endpoints:GET /v1/ai/routines— List all routinesPOST /v1/ai/routines— Create a new routineGET /v1/ai/routines/{routineId}— Get routine detailsPUT /v1/ai/routines/{routineId}— Update a routineDELETE /v1/ai/routines/{routineId}— Delete a routine
Permissions
Creating a routine requires a restricted querier role or above. Each routine runs with the same permissions as the user who created it, so a routine can only query data its creator has access to. The Routines page is scoped per user — you see the routines you created, while admins can see every routine in the organization.Best practices
- Be specific in your prompts — Clear, detailed instructions produce more consistent results across automated runs
- Test before scheduling — Run your prompt in the Omni Agent first to verify it produces the result you expect before creating a routine
- Choose appropriate schedules — Match the routine’s frequency to how often the underlying data changes and when the result is useful
- Review results regularly — Check routine output periodically to make sure it still meets your needs as your data and questions evolve

