The Pipedrive integration allows agents to view and manage Pipedrive people, organizations, and deals from the BoldDesk Ticket, Contact, and Contact Group modules. Errors can occur when required values are missing, field values exceed supported limits, or linked Pipedrive records no longer exist.

This article explains common Pipedrive integration errors and the actions required to resolve them.

For installation and configuration instructions, learn more on How to Set up Pipedrive App with BoldDesk.

Prerequisites

Before troubleshooting a Pipedrive integration error, ensure that:

• The Pipedrive app is installed and authorized in BoldDesk.
• The connected Pipedrive account is active.
• The agent has permission to access the Pipedrive app.
• The agent has access to the applicable BoldDesk brand.
• The required Pipedrive fields are configured for display in BoldDesk.
• The person, organization, pipeline, stage, or deal referenced by the operation exists in the connected Pipedrive account.

Identify the Affected Pipedrive Record

The location of the error may depend on the Pipedrive record being created, viewed, or linked.

Before correcting the error, confirm that you are working with the correct Pipedrive account and record type.

Resolve Required-Field Errors

Required-field errors occur when an operation is submitted without a value that Pipedrive requires.

Resolve Email Validation Errors

1. Invalid Email ID
   The Invalid email ID error indicates that the submitted email address is incomplete or uses an unsupported format.
   Enter a valid email address, such as: [email protected]
   Before retrying the operation, confirm that the email address:

   • Contains a valid value before the @ symbol.
   • Contains a valid domain after the @ symbol.
   • Does not contain leading or trailing spaces.
   • Does not contain multiple email addresses in one field.
   • Does not contain unsupported characters.

2. Email Can Be a Maximum of 100 Characters
   The following error appears when the submitted email address contains more than 100 characters:
   Email can be maximum 100 characters long.
   Shorten or correct the email address so that it contains no more than 100 characters, and then retry the operation.

Resolve an Invalid Close Date

The following error indicates that the close date supplied for a Pipedrive deal is invalid:

Invalid close date.

The error may occur when the value:

• Does not represent a valid calendar date.
• Uses an unsupported date format.
• Contains additional text or unsupported characters.
• Cannot be applied to the selected deal.

To resolve the error:

1. Confirm that the value represents a valid calendar date.
2. Remove unsupported text or characters.
3. Enter the date using the format accepted by the integration.
4. Confirm that the selected Pipedrive deal can be updated.
5. Retry the operation.

If the value is submitted through an API or custom integration, verify the required date format in the applicable API documentation.

Resolve Field-Length Errors

The following error indicates that the submitted field value exceeds the maximum supported length:

(fieldName) can be maximum 255 characters long.

The actual field name replaces (fieldName) when the error is displayed.

Resolve Deal-Value Errors

The following error indicates that the submitted deal value is outside the supported numeric range:

Deal value has to be within the range of -9007199254740991 to 9007199254740991.

Use a value within the following range:

Before retrying the operation, confirm that:

• The value is numeric.
• The value falls within the supported range.
• The decimal and thousands separators are valid.
• The value does not contain a currency symbol or unsupported text.
• The applicable currency is selected separately, where required.

Resolve Missing Pipedrive Record Errors

A missing-record error occurs when a Pipedrive record referenced in BoldDesk does not match an active record in the connected Pipedrive account.

Resolve a Missing Pipedrive Organization

The following error means that the organization linked to a BoldDesk Contact Group does not match an active organization in the connected Pipedrive account:

Organization doesn't exist in Pipedrive.

The error may occur when the organization:

• Was deleted.
• Was merged into another organization.
• Was archived.
• Belongs to another Pipedrive account.
• Was linked using an incorrect organization ID.
• Is inaccessible to the connected Pipedrive user.

To verify and relink the Organization:

1. Sign in to Pipedrive.
2. Go to Contacts → Organizations.
3. Search for the required organization.
4. Open the organization.
5. Confirm that the organization is active.
6. Copy the organization’s numeric ID from the Pipedrive URL.
7. Return to the applicable Contact Group in BoldDesk.
8. Open the Pipedrive app.
9. Relink the Contact Group using the correct organization.

If the organization was merged, link the BoldDesk Contact Group to the remaining active organization.

If the organization was deleted and must still be used, recreate it in Pipedrive before linking it again.

Resolve a Missing Pipedrive Person

The following error means that the person linked to a BoldDesk contact does not match an active person in the connected Pipedrive account:

Person doesn't exist in Pipedrive.

The error may occur when the person:

• Was deleted.
• Was merged into another person.
• Belongs to another Pipedrive account.
• Was linked using an incorrect person ID.
• Is inaccessible to the connected Pipedrive user.

To verify and relink the person:

1. Sign in to Pipedrive.
2. Go to Contacts → People.
3. Search for the person using the name or email address.
4. Open the matching person.
5. Confirm that the person is active.
6. Copy the person’s numeric ID from the Pipedrive URL.
7. Return to the applicable contact or ticket in BoldDesk.
8. Open the Pipedrive app.
9. Relink the BoldDesk contact using the correct person.

If the person was merged, link the BoldDesk contact to the remaining active Pipedrive person.

If the person was deleted and must still be used, recreate the person in Pipedrive before linking the BoldDesk contact again.

Resolve Missing Pipeline or Deal Stage Values

A pipeline or stage selected earlier may become unavailable after it is renamed, deleted, moved, or restricted in Pipedrive.

To verify the pipeline and stage:

1. Sign in to Pipedrive.
2. Confirm that the required pipeline still exists.
3. Confirm that the required deal stage belongs to the selected pipeline.
4. Verify that the connected Pipedrive user has access to the pipeline.
5. Return to BoldDesk and refresh the Pipedrive information.
6. Select an available pipeline and stage.
7. Retry the deal operation.

If the pipeline or stage was removed, select another active value instead of attempting to reuse the deleted reference.

Resolve a Pipedrive Record That Is Not Displayed

If a person, organization, or deal exists in Pipedrive but does not appear in BoldDesk, review the following checks:

The Pipedrive configuration supports selecting fields to display for the following record categories:

• Person Fields
• Organization Fields
• Deal Fields

If the required information is not displayed, review the field-visibility configuration in the Pipedrive app.

Reauthorize the Pipedrive Integration

Reauthorization may be required when:

• The connected Pipedrive session has expired.
• The connected user’s access was revoked.
• The Pipedrive account credentials changed.
• The app was removed from Pipedrive.
• The integration no longer has permission to read or create records.

To reauthorize the integration:

1. Go to Admin → Marketplace.
2. Open the Pipedrive app.
3. Start the available authorization or reauthorization process.
4. Sign in to the correct Pipedrive account.
5. Review and approve the requested permissions.
6. Complete the authorization process.

After reauthorization:

1. Confirm that the Pipedrive app is active.
2. Review the selected field visibility.
3. Review the app permissions and brand access.
4. Open an applicable ticket, contact, or Contact Group.
5. Retry the failed operation.

For complete installation and authorization instructions, refer to How to Set Up the Pipedrive App with BoldDesk.

Collect Information for Further Investigation

If the error continues after correcting the affected field or record link, collect the following information:

Share the collected information with BoldDesk Support through the approved support channel.

Frequently Asked Questions

1. Why Does BoldDesk Indicate That a Pipedrive Person or Organization Does Not Exist?
   The linked record may have been deleted, merged, archived, created in another Pipedrive account, made inaccessible, or referenced using an incorrect ID.
   Locate the active record in the connected Pipedrive account and relink it using the correct numeric ID.

2. Can I Create Pipedrive Records from BoldDesk?
   Yes. Depending on the selected module and the agent’s permissions, agents can create supported Pipedrive people, organizations, and deals from the Pipedrive app in BoldDesk.
   For detailed usage instructions, learn more on How to Manage Pipedrive Information in BoldDesk.

3. Do I Need to Reinstall Pipedrive When a Required Field Is Missing?
   No. Complete the required field identified in the error and retry the operation.
   Reauthorize the app only when the integration is inactive, unauthorized, or unable to access the connected Pipedrive account.

4. Can I Increase the 100-Character Email Limit by Changing My BoldDesk Plan?
   No. The email-length restriction is a field-validation limit and is not controlled by the BoldDesk subscription plan.

5. Can I Increase the 255-Character Field Limit?
   No. Shorten the affected field value to 255 characters or fewer.

6. Does Changing the BoldDesk Plan Resolve Pipedrive Validation Limits?
   No. Required-field rules, email-length limits, general field-length limits, and the supported deal-value range are data-validation restrictions. Changing the BoldDesk plan does not increase them.

Related Articles

1. How to Set up Pipedrive App with BoldDesk
2. How to Manage Pipedrive Information in BoldDesk
3. Common Integration Errors and Resolution in BoldDesk
4. Managing App Permissions and Visibility in BoldDesk