Sharing content with schedules & alerts

JustAsk offers two ways to automate sharing content:

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

Destinations

Note

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 both email and Amazon S3, you’ll need to create two deliveries.

A destination is the channel or service JustAsk will send deliveries to. Your admin can enable and disable the following destinations:

Destination	How it works
Email	Sends an email to one or more recipients. Recipients can be other users in your JustAsk organization or non-users, such as an external stakeholder.
Amazon S3	Delivers content to an Amazon S3 bucket using cross-account IAM role assumption. AWS IAM setup is required prior to use.
SFTP	Delivers content to an existing SFTP server.
Webhook	Sends a request to a webhook URL, such as a Zapier webhook. Recipients are determined by the webhook’s configuration.

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, JustAsk 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:

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

Note

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 - Your admin controls whether deliveries are allowed by default.
• 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.

If you don’t see the option to create deliveries, contact your admin.

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, JustAsk creates or updates a cache entry from that run.

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, JustAsk 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.