Skip to main content
A delivery sends Omni content, such as a dashboard or a single tile, to a destination like email or Slack. Deliveries run automatically, either on a schedule or only when your data meets a condition, so your team stays informed without requesting reports.
Check out our Alerts for operational workflows blog post to see how some Omni customers use alerts!

How it works

There are two ways to automate content sharing in Omni:
  • Schedules, which deliver content at specified frequencies. Note that delivery times are approximate and happen within 15 minutes of the specified time.
  • Alerts, which deliver content only if specific conditions are met

Supported content

The following content types can be used in deliveries:

Destinations

A destination is the channel or service Omni will send deliveries to. Organization Admins can enable and disable the following destinations in Settings > Deliveries:
A delivery can only have one destination. To deliver to multiple destinations, you’ll need to create a delivery for each destination. For example, to deliver a dashboard to email and Slack, you’ll need to create two deliveries.

Embedded content

Deliveries are supported in embedded Omni instances. See Configuring deliveries in embedded Omni for more information. If the [delivery settings]((#delivery-access) are enabled and you don’t see a way to create deliveries in your embedded instance, reach out to Omni support.

Alert condition types

When you create an alert, you choose a small Results to check query. On each scheduled run, Omni runs that query and evaluates a condition against its results. The Results to check query always runs fresh, regardless of the delivery’s cache setting. Only the content sent once the condition is met can use cached results. If the condition is met, the full delivery is sent. If not, the run is recorded as a successful “condition unmet” outcome and nothing is delivered. You’ll select one of the following condition types when configuring an alert:
First-run behavior for “Results have changed” and “Results have stayed the same”: On the very first run, there’s no previous result to compare against, so the condition evaluates to false and no delivery is sent. The first run establishes a baseline; alerts can fire starting on the second run.

Delivery access

The ability to create deliveries can be controlled through instance and document-level settings:

Data and permissions in deliveries

All queries in a delivery run using the schedule creator’s identity and user attributes at the time the delivery runs. Every recipient receives the same content — the data the creator can access, shaped by the creator’s user attributes and any access filters applied to their account at that time. Email deliveries support a Personalize delivery with the recipient’s user attributes option. When enabled, each recipient receives content filtered by their own user attributes at the time the delivery runs, instead of the creator’s. For setup details, see email delivery personalization. If your organization’s Allow user color scheme setting is enabled, a delivery renders in color scheme (light or dark) of the recipient it’s personalized for, or the schedule owner’s otherwise. A recipient or owner set to System, or whose membership no longer exists, gets the organization’s default color scheme instead.

Delivery cache

By default, deliveries skip existing cached results and run fresh queries so recipients see the latest data. Once a delivery’s query completes, Omni creates or updates a cache entry from that run, which is why deliveries are useful for preemptively warming the cache for later interactive users.

Use cached results if available

You can override the default and let a delivery return cached results instead of always querying the warehouse. On the delivery form’s Dashboard tab (or Chart tab, for single-tile deliveries), enable Use cached results if available. When this option is on, the delivery follows the model’s cache policy — if a matching, non-expired cache entry exists, Omni returns it instead of running a fresh query. For alerts, this setting only affects the content sent once the condition is met. The Results to check query always runs fresh, even when Use cached results if available is on.

Restoring deleted deliveries

Deleting a schedule or alert moves it to the trash. To restore a deleted delivery:
  1. Click the Trash option in the main sidebar.
  2. Click the Deliveries tab. This tab is visible only if there is at least one delivery deleted within your organization’s Trash visibility window.
  3. Locate the delivery and click Restore delivery.
Don’t see a delivery? Deliveries only display in the trash if they were deleted within your organization’s Trash visibility window.