If you are experiencing issues with response handlers (e.g Airtable, HubSpot, Zapier), this guide covers common errors and how to fix them.
General Recommendations
To ensure smooth response handling and successful data submission, follow these best practices:
Required Fields: Make sure all required fields contain data before submission.
Conditional Logic: If you're using conditional flows, required fields must be present in every conditional path that leads to submission.
Multiple Submission Buttons: Ensure that required fields are placed before the first submission button, regardless of the path taken.
Data Type Matching: The data type in Heyflow must match the expected format in your integration. Common issues include:
The integration expects a number, but a text input is provided.
A field uses an incompatible number format (e.g. comma vs. dot).
The integration expects a specific value, but receives something else.
A value selected from a list doesn't match the expected list of values in the integration.
Validation Settings: Use validation options like "Auto-remove spaces" to clean up user input before sending it.
Authentication: Re-authenticate integrations regularly to prevent issues caused by expired tokens.
Cannot find access token for user
Description: This is an authentication issue with the integration. It typically occurs when the OAuth token required to connect Heyflow to a service (e.g., HubSpot or Airtable) is missing or expired.
Solutions:
Reconnect the integration from the Integrations panel.
Ensure that the user who originally authorized the integration still has valid access.
How to Reauthorize a Third-Party Integration
If you encounter an error like “Cannot find access token for user”, it typically means that the authentication token has expired or is no longer valid.
To reauthorize access and restore the integration, follow these steps:
Go to the Integrations tab in your Heyflow account.
Select your integration and click on ‘Manage accounts’.
A pop-up will open where you can then click on ‘Reconnect’.
Now you are ready to receive new responses correctly.
This process will refresh the token and re-establish the connection with the third-party service.
VALIDATION_ERROR: Property values were not valid
Description: The value submitted by Heyflow does not match the format or expected value of the mapped property in the target platform (e.g., HubSpot). There are some common scenarios you'd want to check:
Options mismatch
For dropdown or multiple choice fields, ensure the label in Heyflow exactly matches the internal value in the target system — including upper/lower case.
Text vs. numbers
Ensure numeric fields contain only numbers. In Heyflow, you can do this by selecting a “Number” input field instead of a regular “Text” field. To do this:
Select the input field in your flow.
In the left sidebar, scroll down to the Advanced section.
Locate the option Native input type.
From the dropdown, select number.
This ensures that only numeric values are submitted, preventing format errors in the target platform.
Email format errors
Make sure the email input is correctly formatted.
In Heyflow, you can enforce this by enabling the “Enforce email pattern” option in the input field settings. This prevents users from submitting invalid email formats.
To enable this:
Select the input field where users will enter their email address.
In the left sidebar, scroll down to the Validation section.
Check the box labeled “Enforce email pattern”.
Example:
VALIDATION_ERROR: Property values were not valid:[{"isValid":false,"message":"Email address [email protected] is invalid","error":"INVALID_EMAIL","name":"email"}]
Solution:
Match input values to expected values exactly.
For emails, enable “Auto-remove spaces” under the "Decorators" settings.
Re-test the flow after publishing changes.
Other Error Messages
Some integrations work a bit differently from the ones covered above (like HubSpot or Airtable). If you're using a different integration and encountering a specific error message, check out the following articles for more tailored help: