Connect Tableau to your Outpost data

This guide covers how to connect Tableau to the files Outpost delivers, plus how to handle scheduled extract refresh and when you actually need Tableau Bridge.

SharePoint or OneDrive

The smoothest path for Microsoft 365 shops. Use the OneDrive and SharePoint Online connector that ships with Tableau Desktop and Tableau Cloud.

In Outpost:

1. Open the wizard, select your saved search or dataset
2. Choose SharePoint or OneDrive as the destination
3. Authenticate with your Microsoft 365 account
4. Pick the folder and filename, schedule, save

In Tableau Desktop:

1. Connect → To a Server → OneDrive and SharePoint Online
2. Sign in with your Microsoft 365 account
3. Browse to the file Outpost delivers
4. Drag it to the canvas, set up joins or relationships as usual
5. Switch the connection from Live to Extract (top-right of the data source page)
6. Publish the workbook (or just the data source) to Tableau Cloud or Tableau Server

Scheduled extract refresh:

1. In Tableau Cloud or Server, find the published data source
2. Refresh Schedules → New Schedule (or attach to an existing one)
3. Set the refresh to run 15–30 minutes after Outpost delivers
4. Set up alert subscriptions for refresh failures

Tips:

• Use Extract, not Live, for file-based sources. Live mode re-reads the file every time someone touches the dashboard.
• Schedule extract refresh 15–30 minutes after Outpost delivers. SharePoint indexing can lag, and a tight schedule will occasionally pull yesterday's file.
• Use a service account in production. Personal credentials break when people change role.
• Publish the data source separately from the workbook. One published data source can feed many dashboards. Transforms happen once instead of in every workbook.
• Route extract refresh failure alerts somewhere a human will see. Personal email gets ignored.

Google Drive

Tableau has a first-party Google Drive connector, which makes this path straightforward for Google Workspace shops.

In Outpost:

1. Choose Google Drive as the destination
2. Authenticate, pick the folder, schedule

In Tableau Desktop:

1. Connect → To a Server → Google Drive
2. Sign in with the Google account that has access to the folder
3. Browse to the file
4. Connect, set up the data source, switch to Extract, publish

Scheduled refresh:

• In Tableau Cloud, the Google Drive connector supports scheduled refresh natively. No Bridge required.
• In Tableau Server, save credentials with the data source.
• Schedule with a buffer after Outpost's delivery time.

Tips:

• Use a service account, not a personal Google account. OAuth tokens tied to personal accounts eventually expire or get revoked.
• Keep the file in a Shared Drive, not a personal My Drive. Shared Drives survive personnel changes.
• Tableau caches credentials per data source. Changing the service account means updating credentials on every published data source. There's no global setting.

NetSuite File Cabinet

Simplest destination in Outpost. Tableau needs the file exposed via a URL to read it, and Tableau has no generic Web connector. Two options:

Option A: Web Data Connector. Use a community Web Data Connector that fetches a CSV from a URL. Adds a third-party piece to your pipeline.

Option B: Sync the file locally first. Use a scheduled task or SharePoint sync to pull the File Cabinet file to a known location, then point Tableau at that local file. Less elegant, no third-party dependency.

Recommendation:if you're a Tableau shop, File Cabinet is the destination of last resort. SharePoint or Google Drive saves you a meaningful amount of plumbing. Outpost lets you change destinations without redoing the setup, so start with SharePoint or Drive and only fall back to File Cabinet if there's a specific reason.

When you need Tableau Bridge

If you're on Tableau Cloud and your Outpost destination is on-premises or behind a firewall, you'll need Tableau Bridge running somewhere in your network to broker the refresh. This applies to:

• Files synced to a local folder via SharePoint sync or Drive for desktop
• File Cabinet URLs that aren't publicly accessible
• Any data source Tableau Cloud can't reach over the public internet

For pure cloud-to-cloud paths (Outpost → SharePoint Online → Tableau Cloud, or Outpost → Google Drive → Tableau Cloud), you don't need Bridge. That's a good reason to prefer those paths in production.

If you do need Bridge:

• Run it on a server, not someone's laptop
• Set it up as a Windows service so it survives reboots
• Monitor it. When Bridge stops, every dependent refresh stops with it.

Common pattern

Outpost delivers each saved search to a dedicated SharePoint or Google Drive folder. Tableau Cloud connects directly using a service account, no Bridge required. Each data source is published once and shared across workbooks. Extract refresh runs 30 minutes after Outpost. Failure alerts go to a shared channel.