Integration connectivity problems

If you're attempting to set up an integration but run into a connection problem, here are some common errors and solutions.

No Results

What This Error Means

When linking an integration in the editor, the system searches for matching records based on your query. The No Results error appears when either of the following is true:

• The connected account has no available records to return
• The autocomplete search query did not find any matching results

When this happens, you will see the following message:

No Results. If you're having issues, see the troubleshooting page.

Troubleshooting Steps

• Ensure your integration has applicable records
• Ensure you're searching for the correct title of the record

CRM Is Not Connected

What This Error Means

The integration hasn't been connected and set up.

Troubleshooting Steps

• Go to the Integrations page and find the integration you wish to connect
• Click on the integration card and begin the connection

Integration Is Paused

What This Error Means

The CRM connection exists, but syncing has been paused.

Troubleshooting Steps

• Go to the Integrations page, and find the connected integration that has been paused
• Click on the integration card, and click resume

Sync Hasn't Completed Yet

What This Error Means

The integration was recently connected, and the initial data sync is still in progress.

Troubleshooting Steps

• Wait for the initial sync to finish, then search again

Record Doesn't Exist in the CRM

What This Error Means

The record was never created, or it was created in a different CRM instance.

Troubleshooting Steps

• Confirm the record exists in the CRM instance connected to Proposify

Object Type Not Enabled

What This Error Means

The CRM object type (e.g. Accounts, Contacts, Deals) isn't enabled or mapped in the Proposify integration settings.

Troubleshooting Steps

• Go to the integrations page to find the integration you're connected to
•  Click on the integration card, select reconfigure
• Find and enable/map the object type you're searching for

Search Requires at Least 3 Characters

What This Error Means

The search only happens once you've entered a minimum of 3 characters.

Troubleshooting Steps

• Enter at least 3 characters in the search field

Search Term Doesn't Match the Record Label

What This Error Means

The search is keyword-based and only matches against the record's label field.

Troubleshooting Steps

• Search using the exact title/label of the record as it appears in the CRM

Record Is in a Different Workspace or Account

What This Error Means

You may be searching in the wrong Proposify workspace, or the CRM has multiple orgs/instances and the wrong one is connected.

Troubleshooting Steps

• Confirm you're working in the correct Proposify workspace
• Confirm the correct CRM org/instance is connected

Sync Filters Are Too Narrow

What This Error Means

The integration is set up to only sync a subset of records (e.g. deals in a certain pipeline, or contacts owned by specific users), and this record falls outside those filters. Both HubSpot and Salesforce let you configure which records sync at the connector level.

Troubleshooting Steps

• Check the sync filters inside your CRM connector settings and adjust them to include the record

Insufficient CRM Permissions

What This Error Means

The CRM user account used to connect to Proposify doesn't have permission to access certain records or object types. This is configured on the CRM side.

Troubleshooting Steps

• Check with your CRM admin to confirm the connected CRM user account has permission to access the record and object type

Recently Created or Modified Record Hasn't Synced Yet

What This Error Means

Depending on your CRM configuration and how much activity is happening in your CRM, your CRM's own field and API limits can be reached. When this happens, a record that was recently created or modified may not appear in Proposify right away.

Troubleshooting Steps

• Review your integration configuration and make sure only the object types you actually need are being synced
• Removing object types you don't need can free up more of your CRM's available capacity for the records that matter
• Keep in mind this varies by CRM, since each provider handles limits differently