Diagnose and resolve the most common HubSpot integration errors in Cotonity, from OAuth failures to property write errors and webhook timeouts.
OAuth and authentication errors
The most frequent connection error is an expired or revoked OAuth token. Tokens expire after a period of inactivity or when a HubSpot admin revokes the Cotonity app in Connected Apps settings. Symptoms include a red Disconnected status on the integration card and 401 Unauthorized errors in workflow run logs. To fix, click Reconnect in Settings → HubSpot and complete the OAuth flow again. If the error persists after reconnecting, check that the HubSpot user performing the OAuth has sufficient permissions for all requested scopes.
Property write errors
Property-related errors typically manifest as 400 Bad Request responses from the HubSpot API. Common causes include writing an invalid enumeration value to a dropdown or radio property, supplying a string to a number field, or attempting to write to a read-only calculated property. Open the failing workflow run in the Cotonity run history, expand the failing action step, and read the full HubSpot error response — it includes the specific property name and the invalid value provided. Cross-check the value against the allowed options in HubSpot's Properties settings and update your field mapping accordingly.
Webhook delivery failures
Webhook-based triggers (form submissions, list membership changes) can fail if Cotonity's webhook endpoint is unreachable or if HubSpot's webhook delivery times out. Cotonity's webhook endpoints have a 10-second response timeout; if initial processing exceeds this, HubSpot marks the delivery as failed and retries up to three times over the following 24 hours. Check the Webhook Delivery Log in Settings → HubSpot → Webhooks to see delivery attempts and their status codes. If you see repeated timeouts, review whether your trigger workflows contain long-running operations that should be deferred to an async step.
Debugging with the API request log
Cotonity records every HubSpot API request made on your behalf in the API Request Log, accessible from Settings → HubSpot → Debug. Each entry shows the endpoint, request payload, response status, response body, and latency. Filter by status code (4xx for client errors, 5xx for server errors) to quickly identify problem areas. You can replay any logged request from the debug console with one click, which is useful for confirming that a configuration fix resolves the error without needing to re-trigger the full workflow. For persistent issues not resolved by the above steps, share the request log export with Cotonity support.