Destinations

An Outpost Connection is a one-time setup that tells Outpost where to put the files it generates. Once a Connection exists, every export template you build can reuse it. You configure credentials once, not once per report.

This section covers each destination type: what it's good for, how to set up the Connection, and the quirks to know about.

Pick a destination

Listed in recommended order. If you're not sure, start with SharePoint.

  • SharePoint. The recommended destination for most production finance reports on Microsoft 365. Survives personnel changes and has the best permissions story.
  • OneDrive. The personal-scope Microsoft 365 alternative. Good for prototypes and individual workflows; fragile for team-owned production files.
  • Google Drive. For Google Workspace shops. Uses a service account, so it survives personnel changes out of the gate.
  • Azure Blob. Object storage for downstream data pipelines and long-term archives. No BI-friendly path; consumers need to pull from the blob.
  • FTP / SFTP. The old reliable for B2B integrations and downstream systems that expect a file dropped on a server.
  • NetSuite File Cabinet. The simplest setup: no credentials, no external network. Limited as a destination for BI consumers.

SharePoint

Set up a SharePoint Connection in Outpost so export templates can write CSV files to a document library.

OneDrive

Set up a OneDrive Connection in Outpost. Good for individual workflows and prototypes; use SharePoint for team-owned production files.

Google Drive

Set up a Google Drive Connection in Outpost using a Google Cloud service account. Write CSV files to a Shared Drive or folder.

Azure Blob

Set up an Azure Blob Storage Connection in Outpost for downstream data pipelines, long-term archives, and non-BI consumers.

FTP / SFTP

Set up an SFTP Connection in Outpost for B2B integrations and downstream systems that expect files dropped on a server.

NetSuite File Cabinet

The simplest Outpost destination. No auth, no external network. Limited as a target for BI consumers.

How Outpost writes files

On every run, Outpost:

  1. Executes the saved search in NetSuite
  2. Serializes the result as CSV
  3. Hands the CSV to the Connection, which writes it to the destination path you configured

Outpost overwrites files in place by default. If you want historical copies, use filename tokens like {date} or {datetime}. See Your first export template for the token reference.

File-drop vs. live connectors

Outpost doesn't build "live" connectors into Excel, Power BI, or Tableau. It writes files to storage you already own, and those tools read the files on refresh. This is a deliberate architectural choice.