Has anyone created a Hubspot destination on Airbyte? Since I am running Airbyte in a private EC2 which I connect to it via VPN, Hubspot cannot connect to

/auth_flow

because my Airbyte is not exposed to public. Is there a work around to it?

Yes, this is a known challenge when using OAuth-based connectors like HubSpot in Airbyte, especially when your Airbyte instance is running in a private environment (such as a private EC2 accessible only via VPN). The HubSpot destination connector in Airbyte requires OAuth authentication, which typically involves redirecting to a publicly accessible

/auth_flow

endpoint on your Airbyte instance for the OAuth handshake. If your Airbyte instance is not publicly accessible, HubSpot cannot complete the OAuth flow, resulting in the issue you described. This limitation has been discussed in the Airbyte community. As of now, there is no official workaround that allows you to complete the OAuth flow for HubSpot without exposing your Airbyte instance to the public internet. The requirement for a publicly accessible

/auth_flow

endpoint is intrinsic to how OAuth works in Airbyte for these connectors. Some users have requested the ability to manually enter access/refresh tokens or use "bring-your-own-credentials" as a workaround, but this functionality was removed in Airbyte 1.4 and later, and currently, the only supported method is through the OAuth flow, which requires public access to the relevant endpoint. The Airbyte team has acknowledged this limitation and discussed possible future improvements, such as a toggle to allow manual credential entry, but there is no confirmed solution yet available in the documentation or community threads [[Bring-your-own-credentials for OAuth2](https://github.com/airbytehq/airbyte/issues/52084)]. In summary, unless you expose your Airbyte instance’s

/auth_flow

endpoint to the public internet, you will not be able to complete the OAuth authentication required for the HubSpot destination connector at this time. If this is a blocker, you may want to follow or contribute to the related feature requests in the Airbyte GitHub repository for updates on this limitation [[Bring-your-own-credentials for OAuth2](https://github.com/airbytehq/airbyte/issues/52084)].

Hi Berke, Hubspot as a destination is available for data activation (reverse ELT) when upgrading to the newer versions of Airbyte

thanks Henry I am aware of this documentation but it didn't help me. I have found the way of retrieving the refresh token via Postman using redirect URL in my Hubspot public app as

localhost

. After that, I have used set up manually in the Hubspot destination inside Airbyte. That way I was able to add the refresh token. This was the solution I found in case anyone else faces the same issue.