Salesforce (OAuth)

Connect FactBranch to your Salesforce CRM using OAuth to securely access your leads, accounts, opportunities, and other Salesforce data. This authentication method provides comprehensive access to your Salesforce org for building powerful integrations.

Once you've connected your Salesforce account, the authentication is stored securely on FactBranch's servers and can be reused across multiple nodes and flows.

In this article you'll learn:

What you can access

With the Salesforce OAuth authentication, FactBranch can:

• Standard Objects - Access Leads, Accounts, Contacts, Opportunities, Cases, and more
• Custom Objects - Read and write data from custom objects you've created
• Reports and Dashboards - Access Salesforce reports and analytics data
• User Information - Read information about Salesforce users and profiles
• Metadata - Access field definitions, object schemas, and org configuration

Permissions granted: Full access to your Salesforce org data (read and write permissions based on your user profile)

Setting up Salesforce OAuth

To create a Salesforce OAuth authentication in FactBranch:

1. Go to your Data Sources dashboard
2. Click Add data source
3. Select Salesforce
4. You'll be redirected to Salesforce's authorization page

Salesforce authorization process

When you click to connect Salesforce, you'll be taken to Salesforce's secure authorization page where you can:

1. Choose your Salesforce org - Select which Salesforce organization to connect
2. Login to Salesforce - Use your Salesforce username and password
3. Review permissions - See exactly what FactBranch can access
4. Grant access - Authorize FactBranch to access your Salesforce data

Salesforce will then redirect you back to FactBranch.

Using the authentication

Once connected, you can use this authentication in:

• REST API nodes - Make requests to Salesforce's REST API

To use the authentication in a REST API node:

1. Create or edit a REST API node in your Flow
2. Go to the Authentication tab
3. Select your Salesforce authentication
4. Configure your API endpoint (e.g. your Salesforce host URL + /services/data/v58.0/sobjects/Account)

Managing your connection

Renaming the authentication

To rename your Salesforce authentication, click Rename next to the title or double-click the title itself. Enter the new name and press Enter to save.

Revoking access

If you need to disconnect FactBranch from your Salesforce account:

1. Go to your Salesforce Setup
2. Navigate to Apps > Connected Apps OAuth Usage
3. Find "FactBranch" and click Block

You can also delete the authentication from your FactBranch Data Sources dashboard.

Troubleshooting

"Access denied" errors

If you get access denied errors: - Verify you have the necessary permissions in your Salesforce org - Check that your user profile allows API access - Ensure you're using the correct Salesforce org/instance

"Authentication expired" errors

OAuth tokens can expire. If this happens: - FactBranch will automatically attempt to refresh the token - If refresh fails, you may need to reconnect your Salesforce account - Go to your Data Sources and reconnect the Salesforce authentication

API limits

Salesforce has daily API call limits. If you encounter limits: - Check your org's API usage in Salesforce Setup - Reduce the frequency of your API calls - Consider using bulk operations for large data sets - Upgrade your Salesforce edition for higher limits

SOQL query errors

If your SOQL queries fail: - Verify field API names are correct (case-sensitive) - Check that you have read access to the objects and fields - Ensure your query syntax follows SOQL standards - Test queries in Salesforce Developer Console first

Sandbox vs Production

If you're connected to the wrong environment: - Revoke the current authentication - Create a new authentication - Make sure you're logging into the correct Salesforce environment (sandbox vs production)

Custom objects and fields

If you can't access custom objects or fields: - Verify the custom objects/fields exist in your org - Check that your user profile has access to these custom elements - Ensure you're using the correct API names (custom objects end with __c)

Security and privacy

• FactBranch follows Salesforce's security best practices for OAuth applications
• Your Salesforce password is never shared with or stored by FactBranch
• Access tokens are stored in a database that is encrypted at rest
• You can revoke access at any time through your Salesforce org settings
• All API requests are made over HTTPS for secure data transmission