Schedule recurring AI-powered tasks to run automatically on your data.
Routines let you schedule AI-powered tasks to run automatically on a recurring basis. Set up a routine once, and Omni runs your prompt through the Omni Agent and delivers the result to the people you choose.A routine can run on a fixed schedule, or only when a condition you define is met. Conditional routines check the condition on the schedule you set and run the prompt only when the condition is true.Unlike a standard schedule that delivers the same static dashboard or file every time, a routine runs a prompt on each execution. The result is a written, plain-language response — a summary, an answer, or an interpretation of what changed — rather than just a refreshed asset.
Routines work best for recurring questions where an AI-written response adds more than a static export would. Scheduled routines suit regular updates; conditional routines suit exceptions that are only worth a message when they happen. 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”
Exception alerts — “When daily active users drop below 1000, notify the product team with a summary of the drop” — a conditional routine that only delivers when the condition is met, instead of every day
Inventory monitoring — “When inventory for any SKU falls under 50 units, email the operations team with the affected SKUs and current stock levels”
Schedule mode — The routine runs your prompt every time the schedule you set occurs.
Condition mode — The routine checks a plain-language condition against your data on the schedule you set, and runs your prompt only when the condition is met. A condition can check a threshold, whether data is present or missing, or whether results changed since the last check.
Each run executes independently and respects your organization’s permissions and data access controls. The result is delivered as text to the destination you choose — by email, or to a Slack channel or users.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.
Routine results do not include hyperlinked dashboard links, even when delivered to Slack.
Typing a skill’s /identifier anywhere in a routine’s prompt runs that saved skill, resolved as the routine owner each time the routine fires. If the prompt names a skill owned by someone else, the routine’s create/edit form shows a message naming the owner, since that owner’s future edits to the skill change what the routine delivers. If the identifier can’t be resolved when the routine fires — for example, the skill was deleted or renamed — the run continues and the delivery names the skill it couldn’t find.
Restricted Querier permissions or higher are required to create routines. This also requires the Use routines custom role permission. External users can’t create routines, regardless of their connection role.
Routines can be created by asking the agent, in the Omni UI, through the API, or from the Omni CLI.
Omni Agent
Omni UI
API
CLI
Ask for anything recurring and the agent will set up the routine for you:
“Every Monday at 9am, email me a summary of last week’s signups”
You can also add a condition to the routine, so that the routine will run only if the condition is met:
“Every day at 9AM, check if inventory for any SKU falls under 50 units and then email me”
The routine will be created and immediately active, use the model and topic the conversation is scoped to, and run with your permissions. Results are delivered to you unless you say otherwise — name other people, a user group, or a Slack channel in your prompt to deliver elsewhere. Naming several people delivers to a Slack group direct message, up to 8 people. Slack delivery requires a connected Slack workspace.In the Omni Agent, the new routine appears as a card in the conversation. Click Edit routine to open it in split view beside the chat, where you can review and adjust the prompt, schedule, destination, and recipients.You can do this anywhere you can talk to the Omni Agent:
MCP — through the askOmni tool, from an MCP client like Claude or Cursor
API — submit the prompt as an AI job with POST /api/v1/ai/jobs
Omni CLI — submit the same job with omni ai job-submit
1
Define the routine's settings
To quickly create a new routine, click the New button in the sidebar, then select Routine. The New routine form will display.You can also create a routine from the Routines page:
The Routines sidebar item may display differently or not at all if your organization uses a custom sidebar.
Click New routine.
Fill in the fields:
Name — A descriptive name for the routine
Instructions — The instruction the Omni Agent runs on each execution. Write the instructions the same way you would in a chat with the Omni Agent. Include a skill /identifier to run the skill as part of the routine.
Model — The data model the routine queries, with an optional Topic to focus query generation
2
Define the trigger
In the Trigger section, choose how the routine runs:
On a schedule
Run at regular intervals
Schedule mode allows you to run the routine on a fixed cadence. Use the Runs and On sections to specify when the routine should check if the condition is met.
Visual schedule builder
Custom cron schedule (Advanced)
Use the UI options (Daily, Weekly, etc.) to select a time period. Clicking Custom will prompt you to create a cron schedule.By default, schedules are set to send in the local timezone of the creating user’s computer. Use the Times are in drop down to change the timezone.
In the Runs section, click Custom to create a cron schedule.A cron expression is a string that describes the individual details of a schedule:
Order
Unit
Allowed values
Allowed special characters
1
minute
0-59
* , - /
2
hour
0-23
* , - /
3
day of month
1-31
* , - / L W ?
4
month
1-12 or JAN-DEC
* , - /
5
day of week
1-7 or SUN-SAT
* , - / L W ?
6
year
any
* , - /
Using cron, you can create schedules like the following:
At 9:00 AM every day
0 9 ? * * *
At 6:30AM on the last day of the month
30 6 L * ? *
At 8:45 AM every day, Monday through Friday
45 8 ? * MON-FRI *
Omni uses Amazon Web Services’ (AWS) syntax for cron expressions. Refer to the AWS documentation for more information. By default, the most frequent you can configure a schedule is hourly.
Click the icon in the Cron string field to generate a cron schedule from a prompt like “every weekday at 9AM” or “first Monday of each month at noon”.
When something happens
Check at regular intervals if a condition is met, and run when it is
Condition mode allows you to specify when the routine should check if a condition is met, and run if it has.
1
Write the condition
In the Watch for field, write a plain-language description of the condition that must be met for the routine to run, such as:
“When daily active users drop below 1000”
“When inventory for any SKU falls under 50 units”
“When the list of overdue invoices changes from the last check”
Conditions must reference data from your models. Conditions that don’t read any model data - like constant expressions - are not supported.
2
Test the condition
Click Test condition. Omni will attempt to create a query based on the condition and run it against your data warehouse.
Successful check
Failed check
If Omni understands the condition and can create an executable query, a success message will display confirming the condition:
Successful condition check
To see the exact query Omni runs when it executes the routine, click Preview query to open the query in a workbook.
If the check fails, Omni will display a message detailing the reason for the failure:
Failed condition check
When this occurs, modify the condition prompt and click Test condition to run the check again. The condition must pass validation before you can save the routine.
A test may reuse a cached result from a recent, identical test. The routine’s scheduled checks always query your warehouse directly, so a live check can return a different result than a cached test.
3
Define when to check the condition
Use the Checks and On sections to specify when the routine should check if the condition is met.
Visual schedule builder
Custom cron schedule (Advanced)
Use the UI options (Daily, Weekly, etc.) to select a time period. Clicking Custom will prompt you to create a cron schedule.By default, schedules are set to send in the local timezone of the creating user’s computer. Use the Times are in drop down to change the timezone.
In the Checks section, click Custom to create a cron schedule.A cron expression is a string that describes the individual details of a schedule:
Order
Unit
Allowed values
Allowed special characters
1
minute
0-59
* , - /
2
hour
0-23
* , - /
3
day of month
1-31
* , - / L W ?
4
month
1-12 or JAN-DEC
* , - /
5
day of week
1-7 or SUN-SAT
* , - / L W ?
6
year
any
* , - /
Using cron, you can create schedules like the following:
At 9:00 AM every day
0 9 ? * * *
At 6:30AM on the last day of the month
30 6 L * ? *
At 8:45 AM every day, Monday through Friday
45 8 ? * MON-FRI *
Omni uses Amazon Web Services’ (AWS) syntax for cron expressions. Refer to the AWS documentation for more information. By default, the most frequent you can configure a schedule is hourly.
Click the icon in the Cron string field to generate a cron schedule from a prompt like “every weekday at 9AM” or “first Monday of each month at noon”.
3
Configure a destination
In the Deliver to section, select where the results of each run should be delivered:
Email - Select the users or user groups to notify
Slack - Select a channel, one user, or up to 8 users. Selecting more than one user delivers the result as a single shared group direct message, which requires your organization’s Slack app to have the mpim:write scope; without it, you can select only one user. Slack requires a connected Slack workspace; to deliver to a private channel, invite the Omni Slackbot to it first.
4
Save the routine
When finished, click Save routine.
Use the Create an AI Routine API to create a new routine. The routine will run with the same permissions as the authenticating user.You can also include skills as part of a routine by including a skill’s /identifier anywhere in the prompt. The skill will run as the routine’s owner whenever the routine is triggered.
Scheduled routine
Conditional routine
curl --request POST \ --url https://{your-omni-instance}.omniapp.co/api/v1/ai/routines \ --header 'Authorization: Bearer {token}' \ --header 'Content-Type: application/json' \ --data '{ "destination": { "type": "email", "recipientEmails": [ "blob.ross@blobsrus.com", "blob.the.builder@blobsrus.com" ], "userGroupIds": [ "550e8400-e29b-41d4-a716-446655440000" ] }, "modelId": "3c90c3cc-0d44-4b50-8888-8dd25736052a", "name": "Blob Sales morning sales brief", "prompt": "Summarize yesterday's closed-won deals by rep and flag any account that slipped to next quarter,", "schedule": "0 9 ? * * *", "timezone": "America/New_York", "branchId": "3c90c3cc-0d44-4b50-8888-8dd25736052a", "description": "Overview of yesterday's deals, including flags for slipped accounts.", "topicName": "sales"}'
To create a conditional routine, include a condition in the request body:
curl --request POST \ --url https://{your-omni-instance}.omniapp.co/api/v1/ai/routines \ --header 'Authorization: Bearer {token}' \ --header 'Content-Type: application/json' \ --data '{ "name": "Weekly user signups", "modelId": "770e8400-e29b-41d4-a716-446655440002", "prompt": "How many users signed up last week?", "schedule": "0 9 ? * MON *", "timezone": "America/New_York", "condition": { "conditionPrompt": "Run when more than 1000 users sign up in a single week" }, "destination": { "type": "email", "recipientEmails": [ "blob.ross@blobsrus.com", "blob.the.builder@blobsrus.com" ] }}'
To update a routine from chat, you must have the routine open in split view. Click Edit routine on a routine card to open the routine’s edit form beside the chat, then ask the agent to modify specific settings. For example:
“Update the Weekly Signups routine to run at 9AM instead of 8AM”
If the routine delivers to a Slack group direct message, you can add or remove people by name without resetting the rest of the group:
“Also DM Blobby about this”“Stop sending this to Blob Ross”
The agent can only update the routine currently open in the split view — asking about a different routine in a general chat conversation won’t work, even if you created that routine earlier in the session.When you ask the agent to update a routine, it renders an “update routine” chip in the conversation summarizing what changed. The edit form updates live to match the agent’s changes, so you can see your modifications take effect immediately.
Ask the agent to find or list your routines, for example:
“What do I have scheduled?”“Open the Monday routine that posts to #growth”
The agent returns up to 10 matching routines. Click the routine to open it in split view beside the chat. On surfaces that can’t show split view, such as the Omni Slack Agent or an MCP client, each result includes an edit link instead.
Routines cannot edit dashboards. They can only inspect and report on a dashboard referenced in a prompt.
Each routine delivers to a single destination. To send a run to both email and Slack, create one routine per destination.
Routine chat tools aren’t supported for embedded instances using single content mode, scheduled routine runs, and API jobs that run on behalf of embed users.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.
