OAuth authentications allow you to securely connect FactBranch to various services without sharing your passwords. Instead of storing credentials, OAuth uses secure tokens that can be revoked at any time.
This page provides an overview of OAuth authentication in FactBranch. For detailed setup instructions, see the specific service documentation linked below.
In this article you'll learn about:
Available OAuth integrations
FactBranch supports OAuth connections to the following services:
CRM & Sales
- HubSpot - Connect to your HubSpot CRM for contacts, companies, and deals
- Salesforce - Access your Salesforce org data including leads, accounts, and opportunities
- Zendesk Sell - Connect to your Zendesk Sell CRM
Google Services
- Google Sheets - Read data from your Google Sheets spreadsheets
- Google Docs - Access your Google Docs documents
- Google BigQuery - Connect to your BigQuery data warehouse
Marketing & Communication
- Constant Contact - Access your email marketing contacts and campaigns
- Zendesk - Connect to your Zendesk Support instance
Other Services
- Autodesk - Access your Autodesk account data
We're constantly adding new OAuth integrations. If you need a service that's not listed, please contact support@factbranch.com.
How OAuth works in FactBranch
OAuth authentication follows a secure, industry-standard process:
- Authorization Request - You click to connect a service in FactBranch
- Service Login - You're redirected to the service's secure login page
- Permission Review - You review and approve what FactBranch can access
- Token Exchange - The service provides FactBranch with a secure access token
- Secure Storage - FactBranch stores the token securely, encrypted at rest
Benefits of OAuth
- No password sharing - Your passwords never leave the service's secure environment
- Granular permissions - You control exactly what FactBranch can access
- Revokable access - You can revoke access at any time from the service's settings
- Automatic token refresh - FactBranch automatically maintains your connection
Setting up OAuth authentication
The general process for setting up OAuth authentication is:
- Go to your Data Sources dashboard
- Click Add data source
- Select the service you want to connect to
- Follow the OAuth authorization flow
- Use the authentication in your nodes
For detailed, service-specific instructions, see the individual documentation pages linked above.
Using OAuth authentications
Once you've set up an OAuth authentication, you can use it in:
- Service-specific nodes - Like Google Sheets nodes for Google Sheets authentication
- REST API nodes - For custom API requests to the service
- Multiple flows - Reuse the same authentication across different flows
To use an OAuth authentication in a node:
- Create or edit a node in your Flow
- Go to the Authentication tab
- Select your OAuth authentication
- The node will automatically use the OAuth token for requests
Managing OAuth connections
Renaming authentications
To rename any OAuth authentication, click Rename next to the title or double-click the title itself. Enter the new name and press Enter to save.
Revoking access
You can revoke OAuth access in two ways:
- From FactBranch - Delete the authentication from your Data Sources dashboard
- From the service - Revoke access through the service's account settings (recommended for security)
Token refresh
OAuth tokens can expire, but FactBranch automatically handles token refresh for most services. If automatic refresh fails, you may need to reconnect the authentication.
Troubleshooting OAuth issues
"Authentication expired" errors
If you encounter authentication expired errors:
- FactBranch will attempt to automatically refresh the token
- If refresh fails, reconnect the authentication from your Data Sources dashboard
- Check if you've revoked access from the service's settings
"Access denied" errors
If you get access denied errors:
- Verify you have the necessary permissions in the connected service
- Check that your account subscription includes the features you're trying to access
- Ensure you're connected to the correct account/organization
Connection issues
If you can't establish a connection:
- Make sure you're logged into the correct account before authorizing
- Check if your organization has restrictions on third-party app access
- Try using an incognito/private browser window to avoid cached login sessions
Service-specific issues
For detailed troubleshooting of specific services, see their individual documentation pages linked in the "Available OAuth integrations" section above.
Security and privacy
FactBranch takes OAuth security seriously:
- Encrypted storage - All OAuth tokens are encrypted at rest
- Secure transmission - All API requests use HTTPS
- Minimal permissions - We only request the permissions needed for functionality
- Industry standards - We follow OAuth 2.0 best practices