Skip to main content

​
Testing the File Picker

You can test the File Picker directly in the StackOne dashboard to verify it’s working correctly with your connected accounts.

​
Accessing the File Picker Test

  1. Navigate to Accounts in the StackOne dashboard
  2. Find the linked account you want to test
  3. Click the ellipsis menu (⋯) on the account row
  4. Select Test File Picker (or similar option)
This opens the File Picker interface for that account, allowing you to:
  • Verify the picker loads correctly
  • Test navigation through folders/drives
  • Confirm file selection works
  • Check that selected files return the expected format

​
Common Issues

Possible causes:
  • Invalid or expired session token
  • Missing or incorrect account ID
  • Provider not properly connected
  • OAuth redirect URI misconfiguration
Solutions:
  1. Verify the account is connected and shows a healthy status
  2. Check that the connect session token was created with the correct accountId and provider parameters
  3. Ensure OAuth redirect URIs are properly configured (see OAuth Proxy Redirect)
  4. Check browser console for error messages
Possible causes:
  • Insufficient permissions/scopes
  • Account authentication expired
  • Provider-specific access restrictions
Solutions:
  1. Verify OAuth scopes are correctly configured:
    • SharePoint: Files.Read.All, Sites.Read.All
    • Google Drive: https://www.googleapis.com/auth/drive.readonly
    • Confluence/Notion: Read access to spaces/pages/blocks
  2. Re-authenticate the account if tokens have expired
  3. For Notion: Ensure pages/databases are shared with the integration (Settings → Connections → Share with integration)
  4. Check account status in the dashboard
Possible causes:
  • Provider-specific navigation differences
  • Custom picker behavior for knowledge bases (Confluence/Notion)
Solutions:
  1. Review provider-specific picker behavior:
    • Confluence/Notion: Pages can act as both files and folders
    • SharePoint: Requires site selection before drive/folder navigation
  2. Check the File Picker documentation for provider-specific notes
  3. Verify you’re testing with the correct provider type
Possible causes:
  • Using provider-specific IDs instead of StackOne unified IDs
  • Incorrect field selection in configuration
Solutions:
  1. Ensure you’re using the id field from the picker response (this is the StackOne unified ID)
  2. Use the unified ID with StackOne API endpoints: GET /unified/documents/files/{id}
  3. Don’t use provider-specific IDs directly with StackOne APIs
  4. Check the File Picker output format documentation
Possible causes:
  • Redirect URI not configured in provider OAuth app
  • Redirect URI mismatch between configuration and actual URL
  • Missing redirect URI for File Picker (required for Google Drive, SharePoint, OneDrive)
Solutions:
  1. For Google Drive: Add File Picker redirect URI to your OAuth app configuration
  2. For SharePoint/OneDrive: Ensure redirect URI includes File Picker support
  3. See OAuth Proxy Redirect for detailed setup
  4. Verify redirect URIs match exactly (including protocol, domain, and path)

File Picker Guide

Complete File Picker documentation

Integration Errors

Documents API error codes

OAuth Setup

OAuth redirect configuration

Request Tester

Test Documents API endpoints