Authenticate your first destination
Before Outpost can deliver a file, it needs permission to write to a destination. In Outpost, destinations are stored as Connections. This is a one-time setup per connection.
How connections work in Outpost
Outpost uses OAuth for cloud destinations (SharePoint, OneDrive, Google Drive). You sign in once through the destination's standard sign-in flow, the destination issues Outpost a token, and Outpost stores that token in NetSuite. The token refreshes automatically as long as the underlying account stays active.
For FTP / SFTP, Outpost stores the host, port, username, and key or password you provide. For Azure Blob, Outpost stores the storage account and a SAS token or access key. For the NetSuite File Cabinet, no authentication is needed — Outpost is already running inside NetSuite.
The general flow
- In NetSuite, open Outpost by VCG → Connections
- Click New Connection
- Pick the connection type (File Cabinet, SharePoint, OneDrive, Google Drive, Azure Blob, or FTP / SFTP)
- Follow the sign-in or credentials flow for that destination
- Confirm the connection shows as Connected in the Connections list
Each destination has a few specifics. Pick yours from the list below for the detailed walkthrough:
- File Cabinet (no authentication required)
- SharePoint
- OneDrive
- Google Drive
- Azure Blob
- FTP / SFTP
What happens if a connection's auth expires
OAuth tokens occasionally expire. The most common triggers are a password change on the underlying account, an MFA reset, or IT revoking the token. When this happens, the connection shows as Disconnected in the Connections list, and any export templates using it will fail on their next run.
To fix it, open the connection and click Reconnect. You'll go through the sign-in flow again, and any active export templates will resume on their next scheduled run.
For more on how to recognize and fix this, see When schedules don't run.