Integration Guides
Step-by-step guides for connecting your platforms to BuildForce. Secure OAuth authentication, no credentials stored.
Supported Platforms
BuildForce integrates with the platforms you use to manage customer relationships and operations.
Salesforce
Full SupportConnect your Salesforce orgs including Production, Sandboxes, and Developer Editions. Full metadata access for comprehensive health checks.
Features
Requirements
• Salesforce admin access
• API access enabled in org
• Connected App permissions (automatic)
HubSpot
Full SupportConnect your HubSpot portal to monitor CRM configuration, workflow health, and integration status.
Features
Requirements
• HubSpot admin access
• Professional or Enterprise plan
• API access scope approval
ServiceNow
Full SupportConnect ServiceNow instances for ITSM configuration monitoring, workflow validation, and integration health.
Features
Requirements
• ServiceNow admin access
• API access credentials
• Instance URL configuration
Splunk
Coming SoonConnect Splunk for observability monitoring, search health, and data pipeline validation.
Features
Requirements
• Splunk admin access
• API token generation
• HTTP Event Collector access
How OAuth Connection Works
BuildForce uses OAuth 2.0, the industry standard for secure API authorization. Your credentials are never shared with or stored by BuildForce.
Initiate Connection
Click 'Connect Platform' and select your platform from the dashboard.
Authorize Access
You're redirected to the platform's login page. Sign in and approve the requested permissions.
Secure Token Exchange
BuildForce securely exchanges authorization codes for access tokens. No credentials are stored.
Connection Active
Your platform is now connected. BuildForce begins indexing metadata for health checks.
Security Note
BuildForce never sees or stores your platform passwords. OAuth tokens are encrypted at rest (AES-256) and automatically refreshed. You can revoke access at any time from your platform's settings or from BuildForce.
Connection Troubleshooting
Common issues and how to resolve them.
Connection fails with 'Invalid Grant' error
This usually means the authorization code expired. Try the connection process again from the beginning.
Missing permissions after connection
Ensure you're signing in with an admin account that has API access. Some orgs restrict API access to specific users.
Connection shows 'Expired' status
OAuth tokens expire periodically. Click 'Reconnect' to refresh your authorization.
Sandbox connection fails
Make sure you select 'Sandbox' (not 'Production') before initiating the OAuth flow. Sandboxes use different login URLs.
Health check times out
Large orgs with extensive metadata may take longer to scan. Try running checks during off-peak hours.
Need Help with Integration?
Our support team can help you troubleshoot connection issues or answer questions about platform compatibility.