Scheduling deliveries using webhooks
Webhooks are an increasingly common way to trigger exchanges between internet-based services. Webhooks can enable Centricity data delivery to a range of applications. When you set up a delivery, Centricity will prompt you for the webhook address.
Depending on how your organization’s admins have configured your Centricity instance, the default delivery may be email, and this setting may not be visible.
Setting up a webhook
To set up a webhook, go to your web service and follow these steps:
Obtain a URL to which Centricity should send an HTTPS request.
Specify a destination application for your Centricity data delivery. The destination application may require additional configuration in order to receive data from Centricity.
The exact procedure depends on which web service and destination application you use to deliver the data.
Creating and editing schedules
Centricity will prompt you with a pop-up window with your scheduling choices after starting a schedule. For those with permission, you will see the option to deliver to a webhook. The following sections explain the scheduling settings for webhook destinations. For a description of all scheduling options, see the main scheduling documentation page.
Naming your delivery
Name your delivery in the corresponding field at the top of the pop-up window. The title is included in the webhook payload under the “Title” field.
Delivering to webhook
Select “Webhook” in the “Where should this data go?” section. In the “Webhook URL” section, enter the URL where Centricity should send an HTTPS request for this delivery. You can obtain this URL from the web service you’re using to handle your webhook.
Formatting the data
Select your desired data format in the corresponding field. Options for dashboards and Looks are listed below.
Formats for dashboards
PDF: The dashboard in PDF format. The default layout displays tiles as they are arranged in the dashboard, but other layout and sizing options are available under “Advanced Options.”
Visualization: The dashboard visualization in a single image file. The default layout displays tiles as they are arranged in the dashboard, but other layout options are available under “Advanced Options.”
CSV ZIP file: The unformatted data from the dashboard delivered as a collection of comma-separated values (CSV) files in a zipped directory.
Formats for Looks
CSV: The data table as a comma-separated text-file attachment.
XLSX: The data table as an Excel file attachment.
JSON — Simple: The data table as a JSON file attachment. In this format, Looker uses a dimension or measure’s field name as its rendered value rather than the field’s label.
JSON — Detailed, Inline: The data table submitted directly in JSON format, with additional details such as field metadata, cache information, the time when the query was completed, and how long it took the query to run. In this format, Looker uses a dimension or measure’s field name as its rendered value rather than the field’s label.
Text: The data table as a tab-delimited text-file attachment.
HTML: The data table as an HTML file attachment.
Applying filters to the delivery
If you deliver a Look or dashboard with filters, you can filter the results delivered to each set of recipients. For example, you might send regional teams results filtered for their states or counties of interest.
Changing the filter options in the Send or Schedule windows does not change the filters of your Look or dashboard, only the data deliveries you’re editing.