Skip to main content

​
Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Tableau connector page.

​
Automatic webhook setup

StackOne creates and manages the Tableau webhooks automatically when the account is connected, and deletes them when the account is disconnected. You don’t need to create any webhook in Tableau.

  • Tableau allows one event per webhook, so StackOne creates one webhook for each event you enable in StackOne.
  • The webhooks are created on the site the connection signs in to, which is the site set in Content URL.
  • Each webhook is named after its event, for example StackOne WorkbookCreated 1a2b3c4d.

​
Available webhook events

The following Tableau events can be enabled. Only events selected in StackOne get a webhook, and Tableau does not deliver events that have no webhook.

1

Workbook events

Events on published workbooks.

  • Workbook Created (WorkbookCreated) — Fired when a workbook is published to the site
  • Workbook Updated (WorkbookUpdated) — Fired when a published workbook is updated
  • Workbook Deleted (WorkbookDeleted) — Fired when a published workbook is deleted
2

Data source events

Events on published data sources.

  • Data Source Created (DatasourceCreated) — Fired when a data source is published to the site
  • Data Source Updated (DatasourceUpdated) — Fired when a published data source is updated
  • Data Source Deleted (DatasourceDeleted) — Fired when a published data source is deleted
3

Extract refresh events

Events on extract refreshes of workbooks and data sources.

  • Workbook Refresh Started (WorkbookRefreshStarted) — Fired when an extract refresh of a workbook starts
  • Workbook Refresh Succeeded (WorkbookRefreshSucceeded) — Fired when an extract refresh of a workbook succeeds
  • Workbook Refresh Failed (WorkbookRefreshFailed) — Fired when an extract refresh of a workbook fails
  • Data Source Refresh Started (DatasourceRefreshStarted) — Fired when an extract refresh of a published data source starts
  • Data Source Refresh Succeeded (DatasourceRefreshSucceeded) — Fired when an extract refresh of a published data source succeeds
  • Data Source Refresh Failed (DatasourceRefreshFailed) — Fired when an extract refresh of a published data source fails
4

Data label events

Events on data labels of workbooks and data sources. Available on Tableau Cloud only.

  • Label Created (LabelCreated) — Fired when a data label is added to a data source or workbook
  • Label Updated (LabelUpdated) — Fired when a data label on a data source or workbook is updated
  • Label Deleted (LabelDeleted) — Fired when a data label is removed from a data source or workbook
5

User events

Events on users of the site.

  • Admin Promoted (AdminPromoted) — Fired when a user is promoted to a Site Administrator role
  • Admin Demoted (AdminDemoted) — Fired when a user is demoted from a Site Administrator role
  • User Deleted (UserDeleted) — Fired when a user is removed from the site
6

Site events

Events on sites.

  • Site Created (SiteCreated) — Fired when a site is created. Tableau Cloud rejects this event when the webhook is created, so it is not delivered for Tableau Cloud sites
  • Site Updated (SiteUpdated) — Fired when a site’s settings are updated. Tableau Cloud rejects this event when the webhook is created, so it is not delivered for Tableau Cloud sites
  • Site Deleted (SiteDeleted) — Fired when a site is deleted
7

View events

Events on views.

  • View Deleted (ViewDeleted) — Fired when a view is deleted

​
Delivery format

Details of how Tableau delivers events to StackOne.

  • Tableau sends one event per HTTP POST, with the same JSON body for every event: resource, event_type, resource_name, site_luid, resource_luid, created_at and text, a human-readable summary of the event.
  • StackOne uses resource_luid, the LUID of the workbook, data source, user, site or view, as the event ID.
  • For extract refresh events resource is EXTRACTS, and created_at is when the refresh job was created, so the started, succeeded and failed events of one refresh can carry the same created_at.
  • Tableau can deliver one event more than once with an identical body. If a delivery does not get a success response, Tableau retries it three times.
  • Tableau does not sign deliveries and sends no verification request. Each account’s webhooks post to a callback URL unique to that account.

​
Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.