Use this guide when connecting or pushing to Pipedrive, HubSpot, or Zoho CRM does not work as expected.
Test, reconnect, and disconnect
Open Account → Integrations, then Connection details for the CRM you use.
| Action | When to use it |
|---|---|
| Test connection | After changing credentials or scopes in your CRM |
| Reconnect | After regenerating an API token, updating a HubSpot private app token, or when Zoho OAuth expires |
| Disconnect | To remove the integration and stop pushes to that CRM |
Disconnecting does not delete records already created in your CRM.
Enterprise plan required
If you do not see connect or push options, your organization may not be on Enterprise. Open Account → Integrations and check for an upgrade notice. Contact your RUBINLAKE administrator or support if you need access.
Pipedrive issues
Invalid API token
- Confirm you copied the full token from Personal preferences → API
- Make sure the token is from the correct Pipedrive company account
- If you regenerated the token in Pipedrive, click Reconnect in RUBINLAKE and paste the new token
API section missing in Pipedrive
Ask a Pipedrive admin to enable Access their own API token in your permission set under Settings → Manage users → Permission sets.
Wrong company domain
If you entered a company domain, verify it matches your Pipedrive subdomain (for example, acme for acme.pipedrive.com). Try leaving the field empty and connecting again.
HubSpot issues
Invalid or expired private app token
- Open Settings → Integrations → Private Apps in HubSpot
- Confirm the app is still active
- Copy a current token from the Auth tab and Reconnect in RUBINLAKE
Missing scopes
Your private app needs these scopes:
oauthcrm.objects.contacts.readcrm.objects.contacts.writecrm.objects.companies.readcrm.objects.companies.writecrm.schemas.companies.read
Add missing scopes in HubSpot, save the app, then Test connection in RUBINLAKE.
Contact not linked to company
If the contact appears in HubSpot but is not associated with the company:
- Confirm
crm.objects.contacts.writeandcrm.objects.companies.writeare enabled - Push the company to HubSpot before pushing the contact
- Verify your HubSpot user can associate contacts with companies
Zoho CRM issues
OAuth callback failed
- Complete the Zoho consent flow without closing the browser tab early
- Try again in a private window if you use multiple Zoho accounts
- Ensure you approved access for the correct Zoho organization
Token expired or revoked
Open Connection details for Zoho CRM and click Reconnect. Sign in to Zoho and approve access again.
Push failed after successful connect
- Confirm your Zoho user can create and edit Accounts and Contacts
- Check that required modules are enabled in your Zoho CRM edition
Push and credit issues
Push failed with authentication error
Your CRM credentials were rejected during the push. Open Account → Integrations, Reconnect the CRM, then try again.
Charged more credits than expected in bulk push
Bulk jobs charge 1 credit per new record only. Records you already pushed to that CRM are updated for free. The confirmation dialog shows an estimate before you start.
Bulk job limit
Each bulk push supports up to 500 records. Split larger selections into multiple jobs.
Known limitations
- One-way only: data flows from RUBINLAKE to your CRM, not the other way around
- No deals or pipelines: only companies and contacts (plus notes where supported)
- One connection per CRM per organization: shared across users in your RUBINLAKE organization
- No automatic sync: you choose when to push each record or bulk selection
Still need help?
Contact RUBINLAKE support from Account settings or your usual support channel. Include the CRM name, error message, and whether the issue happens on connect or during push.
Was this article helpful?