We are using the Hubspot Connector to fetch data from multiple Hubspot instances. To do this, we are using the OAuth2 process to connect, where you need a user to enter their username/password for Matillion to store the required tokens.
This works for a Public App, however, we sometimes want to use a Private App. Private Apps provide you with an Access Token that you can copy and paste, however, there's no ability in Matillion to paste the Access Token anywhere as part of the authentication options.
https://developers.hubspot.com/docs/api/private-apps#make-api-calls-with-your-app-s-access-token
Please can we get an option to hook into the Private App authentication method?
Hi @djackson and thanks so much for your post.
Could I ask that you raise your idea in our Ideas Portal here please? The team regularly looks at the Ideas posted there for consideration into our product Roadmap. Other community members can also vote and comment on your idea too.
Many thanks!
Claire
I've also run across an issue recently trying to demo the Hubspot connector with a HubSpot developer account. They recently switched from client id / client secret to "Private App" that @djackson mentions above. The Private App only uses a token.
Is there a way to use the "API" option in OAUTH configuration to make the connection work?
@WilliamAubrey Did you find a way to get around this hurdle?
Hi @joseph.lewright ,
I was unable to find a solution. Didn't try testing the generic API option either. This was only a training exercise for me, so I decided to shelve it until the connector is updated. Please do let me know if you find a solution. Thanks for reaching out!
William
I have been playing around with the API query connector. I was able to import a table of companies by doing the following:
- Create a private app in HubSpot
- Grant app all scopes listed here https://developers.hubspot.com/docs/api/crm/companies
- Use bearer token to generate API query profile for companies
- Enable pagination and assign the next item link
- Create a target table in snowflake with the exact column names ex: "properties.name"
- Bingo!
Functionally, it accomplishes the goal I needed it to, but this is quite the workaround to load data from a source Matillion claims it supports.