# Troubleshoot Integrations

Source: https://www.digiparser.com/docs/guides/troubleshooting/integration-problems

Common Problems

# Troubleshoot Integrations

Check why a connected import or export did not run

Copy MarkdownOpen

# [Troubleshoot Integrations](#troubleshoot-integrations)

Feedback

Use this checklist when a connected source does not import a document or processed data does not appear in another app.

## [Cloud storage imports](#cloud-storage-imports)

Feedback

For OneDrive, Google Drive, Dropbox, or Box:

Feedback

1.  Open the parser and go to **Settings -> Integrations**.
2.  Expand the cloud storage import under **Added integrations**.
3.  Confirm that **Monitoring active** appears.
4.  Click **Test folder access**.
5.  Confirm that the file was added after you clicked **Save configuration**.
6.  Check **Include subfolders** if the file is inside a nested folder.

Feedback

Dropbox, Google Drive, and Box are checked every minute, so a new file normally appears within one or two minutes. OneDrive files normally appear within a few minutes.

Feedback

If you see **Needs reconnection**, click **Reconnect**. If you see **Folder unavailable**, restore access or select another folder. If you see **Monitoring failed**, click **Restart** when available or save the configuration again.

Feedback

The integrations do not import files that were already present when monitoring began. Renaming or editing a file that was already imported does not create a second document.

Feedback

See the setup guide for [OneDrive](/docs/guides/integrations/importing-from-onedrive), [Google Drive](/docs/guides/integrations/importing-from-google-drive), [Dropbox](/docs/guides/integrations/importing-from-dropbox), or [Box](/docs/guides/integrations/importing-from-box).

## [Cloud storage exports](#cloud-storage-exports)

Feedback

For Google Drive or Dropbox:

Feedback

1.  Confirm that the integration shows **Configured**.
2.  Click **Test access** to check the selected folder without uploading a file.
3.  Confirm that the original document file is available and no larger than 100 MB.
4.  Check whether the document is waiting for final approval.
5.  Reconnect the account if DigiParser reports an expired connection.

Feedback

With duplicate replacement enabled, Google Drive stops before uploading when several exact-name files exist. Choose a unique filename or remove the ambiguity. If DigiParser reports an unknown upload outcome, check the destination before processing the document again.

## [Export integrations](#export-integrations)

### [Confirm that processing finished](#1-confirm-that-processing-finished)

Integrations run after extraction finishes. If **Reviews & Approvals** is enabled, an export may wait until the document is approved.

Check the document status:

*   **Processing** or **Queued** - Wait for extraction.
*   **In Review** - Complete the required review.
*   **Rejected**, **Skipped**, or **Failed** - The integration normally will not receive a completed result.
*   **Processed / Approved** - Continue with the checks below.

### [Confirm the integration is enabled](#2-confirm-the-integration-is-enabled)

1.  Open the parser.
2.  Go to **Integrations**.
3.  Find the integration under the added or configured integrations.
4.  Confirm that it is enabled and saved.

Integrations are configured per parser. A connection on one parser does not automatically apply to another.

### [Check the connected account](#3-check-the-connected-account)

For Google Sheets and similar services:

*   Reconnect the account if DigiParser shows **Not connected**.
*   Confirm that the connected person can still open the destination.
*   Check whether the password, organization, or account permissions recently changed.

### [Check the destination and mapping](#4-check-the-destination-and-mapping)

*   Confirm that the correct spreadsheet, sheet tab, email address, or automation is selected.
*   Check that every required DigiParser field is mapped to the intended destination field.
*   Update the mapping after renaming or adding parser fields.

An unmapped field is not sent even when extraction succeeds.

### [Test with one document](#5-test-with-one-document)

1.  Use a small document you understand.
2.  Process and approve it if required.
3.  Check the destination.
4.  Compare the extracted values with the integration mapping.

Testing one document makes it easier to distinguish a connection problem from a document-data problem.

### [Avoid duplicate results while testing](#6-avoid-duplicate-results-while-testing)

Reprocessing or resending the same document may create another row or record in the destination.

Before testing again:

*   Check whether the first result arrived late.
*   Use a clearly named test document.
*   Remove any unwanted test row or record from the destination afterward.

## [If the problem continues](#if-the-problem-continues)

Feedback

Record:

Feedback

*   Parser name
*   Document name
*   Approximate processing time
*   Integration name
*   Destination name
*   Any error shown in DigiParser or the connected app

Feedback

Share those details with your team administrator or DigiParser support.

## [Next steps](#next-steps)

Feedback

*   [Integrations Overview](/docs/guides/integrations/overview) - Understand when imports and exports run
*   [Exporting to Google Sheets](/docs/guides/integrations/exporting-to-google-sheets) - Check Sheets setup and mapping
*   [Exporting to Email](/docs/guides/integrations/exporting-to-email) - Check email export setup
*   [Verifying Webhooks](/docs/guides/integrations/verifying-webhooks) - Inspect webhook delivery

How is this guide?

GoodBad

[

Troubleshoot Extraction Accuracy

Fix missing, incorrect, or misplaced extracted values

](/docs/guides/troubleshooting/extraction-accuracy-issues)[

Credits and Billing

Calculate credit usage for processing, AI features, document type rules, classifiers, and reprocessing

](/docs/guides/troubleshooting/credits-and-billing)