Tableau

In Tableau Cloud or Tableau Server, click your avatar in the top-right corner and select My Account Settings. Scroll to the Personal Access Tokens section and click Create new token. Give the token a meaningful name such as 'Bubble Integration' and copy both the token name and the token secret that appear — the secret is shown only once. Store them temporarily in a text file. You will use the token name and secret as the body of your sign-in API call, not as a header. Do not confuse the PAT secret with the session token you will receive in response — the PAT is the long-lived credential you keep safe; the session token is ephemeral and will be stored in Bubble App State.

In your Bubble app, open the Plugins tab in the left sidebar and click Add plugins. Search for 'API Connector' (by Bubble), install it, then close the plugin dialog. Open the API Connector plugin settings. Click Add another API. Name it 'Tableau'. In the Shared headers for this API section, add one header: key is 'Accept', value is 'application/json'. Do NOT mark this header Private — it is not a secret. This Accept header is critical because Tableau's REST API defaults to returning XML. Without it, every response will be XML and Bubble will be unable to parse the fields automatically during initialization. Leave the Authentication field set to None — authentication is handled by the X-Tableau-Auth header added dynamically on each call after sign-in.

1{
2  "api_group": "Tableau",
3  "shared_headers": {
4    "Accept": "application/json"
5  },
6  "authentication": "None"
7}

Inside the Tableau API group, click Add another call. Name it 'Sign In'. Set Method to POST and the URL to 'https://{your-pod}.online.tableau.com/api/3.19/auth/signin' — replace {your-pod} with your actual Tableau Cloud pod identifier (e.g., '10az'). Under Use as, select Action (not Data) — this call will be triggered from a Bubble workflow, not bound to a data source. In the Body section, select JSON and paste the sign-in payload shown below. Replace the placeholder values with your actual PAT name and secret for the purpose of the Initialize call — you can make them dynamic later. Click Initialize call. Bubble will make a real POST to Tableau and parse the JSON response. The response contains 'credentials.token' (the session token) and 'credentials.site.id' (the site UUID). After initialization, go to your Bubble app's Data tab and create two App State variables: 'tableau_session_token' (text) and 'tableau_site_id' (text). Then build a workflow — for example triggered on Page is Loaded — that runs the Sign In action and saves the returned 'credentials token' value to 'tableau_session_token' state and 'credentials site id' to 'tableau_site_id' state. Note: the site ID UUID from the sign-in response differs from the site name you see in the URL — always use the UUID in subsequent API paths.

1{
2  "method": "POST",
3  "url": "https://10az.online.tableau.com/api/3.19/auth/signin",
4  "headers": {
5    "Content-Type": "application/json",
6    "Accept": "application/json"
7  },
8  "body": {
9    "credentials": {
10      "personalAccessTokenName": "BubbleIntegration",
11      "personalAccessTokenSecret": "<your-pat-secret>",
12      "site": {
13        "contentUrl": "mycompany"
14      }
15    }
16  }
17}

Back in the Tableau API group, click Add another call. Name it 'List Workbooks'. Set Method to GET and URL to 'https://{your-pod}.online.tableau.com/api/3.19/sites/<site_id>/workbooks' — note the '<site_id>' placeholder. Set Use as to Data. In the Parameters section, add a parameter named 'site_id' — mark it as a path parameter, not a query parameter. This will be supplied dynamically from App State when the call is made. Now add a header at the call level (not the group level): key is 'X-Tableau-Auth', value is your hardcoded test session token from the sign-in step above. Mark this header Private (click the checkbox). This allows you to initialize the call with a real session token. After initialization succeeds, edit the X-Tableau-Auth header value to be a dynamic value from App State ('tableau_session_token'). Bubble's API Connector supports dynamic headers on calls by switching from static text to a dynamic data reference. The response will nest workbooks under 'workbooks workbook' — Bubble's field detector will map this as a list. Set 'Type of content' to List to enable use in a Repeating Group.

1{
2  "method": "GET",
3  "url": "https://10az.online.tableau.com/api/3.19/sites/<site_id>/workbooks",
4  "headers": {
5    "Accept": "application/json",
6    "X-Tableau-Auth": "<private: dynamic from App State>"
7  },
8  "parameters": {
9    "site_id": "<dynamic: tableau_site_id from App State>"
10  }
11}

Add a third call in the Tableau API group. Name it 'Refresh Workbook'. Set Method to POST and URL to 'https://{your-pod}.online.tableau.com/api/3.19/sites/<site_id>/workbooks/<workbook_id>/refresh'. Add path parameters 'site_id' and 'workbook_id' — both will be supplied dynamically. Add the X-Tableau-Auth header at the call level, marked Private, set dynamically from App State. Set Use as to Action. Leave the body empty — Tableau's refresh endpoint does not require a request body. Click Initialize call using a real site_id and a real workbook_id from your List Workbooks response. The response returns a job object with a job ID — Bubble's workflow will see it as completed. Important: the Tableau workbook refresh is asynchronous. The POST does not wait for the refresh to finish; it returns immediately with a job ID. You cannot poll for completion inside a single Bubble workflow due to Bubble's 30-second workflow timeout. Design your UI to show 'Refresh requested' after the button click rather than waiting for completion. In your Bubble editor, add a button in the Repeating Group of workbooks. In the button's workflow, add step 1: 'Plugins → Tableau - Refresh Workbook', supplying the current row's workbook id and tableau_site_id from App State. Add step 2: 'Element Actions → Set state' to show a 'Refresh requested' text element for that row.

1{
2  "method": "POST",
3  "url": "https://10az.online.tableau.com/api/3.19/sites/<site_id>/workbooks/<workbook_id>/refresh",
4  "headers": {
5    "Accept": "application/json",
6    "X-Tableau-Auth": "<private: dynamic from App State>"
7  },
8  "parameters": {
9    "site_id": "<dynamic: tableau_site_id from App State>",
10    "workbook_id": "<dynamic: current cell's workbook id>"
11  },
12  "body": {}
13}

For display-only use cases — particularly sharing a Tableau Public view or an internally shared Tableau Cloud view with non-technical stakeholders in your Bubble app — you can embed the view without any API calls. In Tableau, open the view you want to share and click Share (top toolbar) → Embed Code. Copy the iframe src URL, which will look like 'https://public.tableau.com/views/{workbook-name}/{view-name}'. In your Bubble app, add an HTML element to the page (from the Visual elements panel in the editor). Set the element's height to a fixed value like 600 or 700 pixels — Bubble's responsive engine does not auto-size iframes. Paste the following HTML, replacing the src with your embed URL. The '?:embed=y&:showVizHome=no' parameters are required to suppress Tableau's navigation bar inside the iframe. Set the element's width to 100% of its container using Bubble's layout settings. Note: private Tableau Cloud reports (not Tableau Public) will show a Google sign-in prompt inside the iframe unless the viewer is already authenticated with the correct Google account in that browser session. This is a Tableau security feature, not a Bubble setting — the only solution is to share the report publicly or use Tableau's Trusted Authentication (advanced, server-level configuration).

1<iframe
2  src="https://public.tableau.com/views/YourWorkbookName/YourViewName?:embed=y&:showVizHome=no"
3  width="100%"
4  height="600"
5  frameborder="0"
6  allowfullscreen>
7</iframe>