Troubleshooting the Documint App

This section provides solutions for addressing some of the most common problems you might face when using the Documint app.

Workflows errors

The Documint app provides a custom workflow action that allows you create documents with your enrolled objects when a workflows is triggered. The created document is stored in a note in your record.

If your document is not being attached, the most likely cause is that the Documint app does not include the required "automation" scope.

You can fix this by re-authorizing the app. From the HubSpot dashboard, go to settings > Integrations > Connected apps > Documint > Actions > Go to settings > Authorize. This will open a frame requiring you to authorize the Documint app.

If this does not solve the problem, it could indicate a deeper problem.

You can find more information on the error by inspecting the record's enrollment history logs. In the "action succeeded" section (action succeeded just means that HubSpot successfully made a request for the Documint action. It does not necessarily mean the action itself was successful) you will find the response error message.

Share the error response with Documint support for a speedy resolution.

Documint card not showing up wiith custom objects

Due to limitations with HubSpot application development, CRM cards can not apply to custom objects. For information on how to work with custom objects in the Documint extension, see Working with Custom Object Data.

Slow document rendering

Document rendering time in Documint can increase not only with template size but also due to several other important factors, particularly when working with the HubSpot extension.

A significant performance factor is the management of associated records. The app retrieves these records in batches of 100 from HubSpot, meaning that even one additional record over this threshold (101 records) would trigger an extra request. Additionally, each different type of associated object requires its own separate request to HubSpot.

To optimize performance, we recommend auditing your record associations. If you find unnecessary or outdated associations that have accumulated over time, removing them can significantly improve rendering speed. This is especially important when dealing with both large quantities of associations and diverse object types.