Sharing content with schedules & alerts

Omni offers two ways to automate sharing content, which can be delivered to platforms like Slack or webhooks:

• Schedules, which deliver content at specified frequencies
• Alerts, which deliver content only if specific conditions are met

Embedded Omni instances also support this functionality.

​

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:

​

Schedule delivery times

Schedules deliver content at specified times. Note that delivery times are approximate and will happen within 15 minutes of the specified time.

​

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:

​

Delivery access

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

• Instance - In Settings > General > Content permissions, Organization Admins can select the default abilities for documents.
• Document - In a saved document, navigate to File > Document Settings to select the abilities other users can have when accessing the document, including whether other users can create deliveries. This applies to both dashboards and workbooks.

Note: for external embed it’s possible an environmental variable has been added to disable scheduling for embed users. If you have checked the Instance and Document level settings to ensure they allow Scheduled Deliveries and still do not see the option for embed users to access the Schedule settings panel please reach out to support.

​

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.

​

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.