Common causes of integration errors
The error message on the integration card specifies the exact failure. Most common causes:
- Expired OAuth token — Google Sheets, Notion, and QuickBooks tokens expire. Re-authenticate via integration settings.
- Invalid webhook URL — Slack or Zapier webhooks may have been deleted or rotated. Update the URL.
- Permission revoked — the connected app had its permissions changed. Re-authorize ParseMe.
- Wrong configuration — incorrect Base ID (Airtable), Spreadsheet ID (Google Sheets), or Database ID (Notion).
- Rate limiting — some services limit push frequency. ParseMe retries with exponential backoff.
How to fix an integration error
- Click the integration edit button and check all configuration fields
- For OAuth integrations, click 'Reconnect' to re-run the authorization flow
- For webhook integrations, copy a fresh webhook URL from your provider
- After saving, use the 'Test push' button to confirm the connection works
- Re-enable auto-push once confirmed
Häufig gestellte Fragen
Do I lose data when an integration errors?
No — failed pushes are logged. Once fixed, you can manually re-push any affected documents from the document detail page.
Will ParseMe retry failed pushes?
Yes — ParseMe retries 4 times with exponential backoff (2, 8, 32 minutes). After 4 failures the integration is set to Error status.
Bereit loszulegen?
Laden Sie Ihr erstes Dokument hoch und erleben Sie KI-Extraktion in Aktion.
Fix your integration