Common Sync Errors

Here are the most common issues and how to resolve them.

"Invalid API Key" or Authentication Errors

Cause: The Kleer API key stored in the integration is invalid or has been revoked.

Solution: Go to the Kleer for HubSpot settings page and re-enter your Kleer API key. You can generate a new key from your Kleer account settings.

"Property Not Found"

Cause: A field mapping references a HubSpot property that doesn't exist in your portal.

Solution: Either create the missing property in HubSpot, or update your field mappings on the settings page to use an existing property.

Records Not Appearing in HubSpot

Possible causes:

• The object type isn't enabled in sync configuration — check the toggle on the settings page
• The sync hasn't run yet — check the sync schedule in How Syncing Works
• Required field mappings aren't configured — some object types require specific fields to be mapped before sync activates

Duplicate Records in HubSpot

Cause: The kleer_id property may not be set on existing HubSpot records, causing the integration to create new ones instead of matching.

Solution: Ensure the kleer_id custom property exists on the relevant HubSpot object type. The integration creates this property automatically during installation, but if it was deleted, records can't be matched.

Workflow Action Not Creating Records

Possible causes:

• The Kleer ID is already set on the enrolled record (the action is idempotent and skips if already created)
• The associated company doesn't have a Kleer client ID — invoices, agreements, and projects require the associated company to exist in Kleer first
• Your plan tier may not include the workflow action you're trying to use

Data Looks Outdated

Cause: Sync runs on a schedule, not in real-time. Changes in Kleer appear in HubSpot after the next sync cycle.

Solution: This is expected behavior. Check the sync schedule for your object type. If you need to trigger an immediate sync, contact support.