Omni offers two ways to automate sharing content, which can be delivered to platforms like Slack or webhooks:Documentation Index
Fetch the complete documentation index at: https://docs.omni.co/llms.txt
Use this file to discover all available pages before exploring further.
- Schedules, which deliver content at specified frequencies
- Alerts, which deliver content only if specific conditions are met
Check out our Alerts for operational workflows blog post to see how some Omni customers use alerts!
Destinations
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.
| Destination | How it works |
|---|---|
| Sends an email to one or more recipients. Recipients can be other users in your Omni organization or non-users, such as an external stakeholder. Supports customizing sender options, such as email domain. Learn more. | |
| Google Sheets | Delivers the contents of a single tile to an existing Google Sheets workbook. Learn more. |
| Amazon S3 | Delivers content to an Amazon S3 bucket using cross-account IAM role assumption. AWS IAM setup is required prior to use. Learn more. |
| SFTP | Delivers content to an existing SFTP server. Learn more. |
| Slack | Delivers content to individual Slack users, public channels, and private channels. Set up in Slack is required prior to use in Omni. Learn more. |
| Webhook | Sends a request to a webhook URL, such as a Zapier webhook. Recipients are determined by the webhook’s configuration. Learn more. |
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. 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:| Condition type | Triggers the delivery when… |
|---|---|
| Results have changed | The Results to check query’s results differ from the previous run |
| Results have stayed the same | The Results to check query’s results match the previous run |
| No results are returned | No rows are returned |
| Any results are returned | At least one row is returned |
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:- Instance - In Settings > General > Content permissions, Organization Admins can select the default abilities for documents.
- Document - In a saved document that has a Dashboard, navigate from the Dashboard to File > Document Settings to select the abilities other users can have when accessing the document.