HubSpot (OAuth)

Connect FactBranch to your HubSpot CRM using OAuth to securely access your contacts, companies, deals, and other CRM data. This authentication method provides comprehensive access to your HubSpot data for building powerful integrations.

Once you've connected your HubSpot 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 HubSpot OAuth authentication, FactBranch can:

• Contacts - Read and write contact information, properties, and associations
• Companies - Access company records, properties, and relationships
• Deals - View and manage deal data, stages, and properties
• Custom Objects - Access custom CRM objects you've created
• Owners - Read information about HubSpot users and team members
• Subscriptions - View subscription and communication preferences

Permissions granted: Read and write access to your HubSpot CRM data, depending on your user permissions in HubSpot.

Setting up HubSpot OAuth

To create a HubSpot OAuth authentication in FactBranch:

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

HubSpot authorization process

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

1. Choose your HubSpot account - Select which HubSpot portal to connect
2. Review permissions - See exactly what FactBranch can access
3. Grant access - Authorize FactBranch to access your CRM data

HubSpot will then redirect you back to FactBranch.

Using the authentication

Once connected, you can use this authentication in:

• REST API nodes - Make requests to HubSpot's 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 HubSpot authentication
4. Configure your API endpoint (e.g., https://api.hubapi.com/crm/v3/objects/contacts)

Managing your connection

Renaming the authentication

To rename your HubSpot 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 HubSpot account:

1. Go to your HubSpot account settings
2. Navigate to Integrations > Connected Apps
3. Find "FactBranch" and click Actions > Revoke

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 HubSpot account - Check that your HubSpot subscription includes the features you're trying to access - Ensure you're using the correct HubSpot portal/account

"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 HubSpot account - Go to your Data Sources and reconnect the HubSpot authentication

Rate limiting

HubSpot has API rate limits. If you encounter rate limiting: - Reduce the frequency of your API calls - Implement delays between requests in your flows - Consider using HubSpot's batch endpoints for bulk operations

Property access issues

If you can't access certain properties: - Check that the properties exist in your HubSpot account - Verify the property names are spelled correctly (case-sensitive) - Ensure your HubSpot subscription includes custom properties if using them

Portal/account selection

If you're connected to the wrong HubSpot account: - Revoke the current authentication - Create a new authentication and carefully select the correct portal during authorization - Make sure you're logged into the correct HubSpot account before authorizing

Security and privacy

• Your HubSpot 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 HubSpot account settings
• All API requests are made over HTTPS for secure data transmission
• FactBranch can only accesses the data scopes you've authorized