Common Issues

Connection issues

OAuth authorization fails or shows a blank screen

This usually happens when third-party cookies are blocked in your browser. Try connecting in a different browser or disable cookie-blocking extensions temporarily. Make sure you're logged into the correct HubSpot portal before starting the OAuth flow.

Connected to the wrong HubSpot portal

During the OAuth flow, HubSpot asks you to select a portal. If you have access to multiple portals, it's easy to pick the wrong one. Delete the credential in Coupler.io and reconnect, selecting the correct portal this time.

Missing data

Some records are missing from the export

Check whether you have active date filters set. If your "Created after" or "Updated after" date is too recent, older records will be excluded. Also confirm that the HubSpot user who authorized the connection has access to those records — private records or team-restricted data won't appear if the authorizing user doesn't have permission.

Custom fields are not appearing in the output

If you specified custom field names manually, make sure you're using the internal HubSpot API field name, not the display label. For example, use top_marketing_challenge not "Top Marketing Challenge". Leave the custom fields input blank to import all custom fields and identify the correct internal names from the output.

Owners or Workflows data is empty

These entities don't support date filtering and the data is returned as-is from HubSpot. If the output is empty, confirm the authorizing user has Super Admin or the appropriate permissions to view users and workflows in that portal.

Permission errors

"Insufficient permissions" error when running the data flow

The HubSpot user who authorized the OAuth connection needs access to the objects you're trying to export. For example, exporting Tickets requires Service Hub access, and exporting Marketing emails requires Marketing Hub access. Reconnect using an account with the appropriate permissions, or ask a Super Admin to authorize the connection.

Data discrepancies

Numbers in Coupler.io don't match HubSpot reports

HubSpot's native reports often apply additional filters, time zones, or attribution logic that isn't reflected in raw API data. Coupler.io pulls unprocessed record data. Check whether the HubSpot report uses a specific pipeline filter, owner filter, or date range that you haven't replicated in your data flow settings.

Field values show IDs instead of readable labels

This is controlled by the Return IDs for lookups instead of labels option in your data flow settings. If this is enabled, lookup fields like deal stage or lifecycle stage will show internal IDs. Disable this option to get human-readable labels instead.

Rate limits

Data flow fails with a rate limit error

HubSpot enforces API rate limits based on your plan. Free and Starter portals have lower limits. If you're pulling large entities like Contacts or Deals with many records, try narrowing the date range using the date filters to reduce the number of records per run. Avoid running multiple HubSpot data flows simultaneously.

HubSpot's API only supports up to 2 active filters at a time. Using both a date filter and an advanced filter counts as 2 filters — adding a third will cause an error.