Hey!
I discover n8n and I’m quite impressed by the possibilities.
I have a question about authentication:
Is it possible to send an API key in query parameter without filling the key directly in the node? An equivalent of “Header Auth” but in query parameter.
Otherwise, as a workaround, is it possible to get the header auth value from an expression to use it as a query parameter?
The Hubspot API requires sending the API key like this (hapikey), and the Hubspot node doesn’t fit my needs.
Not a problem at all, if you look at the post here: Struggling with pagination there is an example workflow that shows how to connect to the Hubspot api using the http request node.
It isn’t a complete example but would get you started.
Out of interest what is missing from the Hubspot node for you?
No sorry, that is currently sadly not supported. As it was however very simply, did I just add support. It will be released with the next n8n version next week. In case you use Docker, you can also use the nightly build n8nio/n8n:nightly which should be available in around 8 minutes.
Thanks a lot @jan for this very quick and effective support!
@Jon, I use Hubspot API to create notes on a contact based on events sent on a webhook by Sendinblue. So I have to make some POST requests on /engagements/v1/engagements: Create an Engagement | Engagements API
In the example workflow that @Jon referred to, I was using a slightly different connection mechanism at the Hubspot end - rather than using the standard API key approach I had created a private app (see help docs here for explanation).
It’s pretty easy to create one of these in Hubspot and it is better because you’ll get a Hubspot access token which is dedicated to your app / integration, otherwise Hubspot seem to only have a single API key to be shared across everything that integrates to the REST API (which is a pain if you ever need to rotate the keys because all integrations have to be changed!).
When using this method instead of putting the hapikey on the url when making your POST, you will need to create an Authorization header with a value of
Hi @scottjscott,
Thanks for the details, I didn’t know it was possible to authenticate with a private app token. This sounds like the perfect solution!
Obviously your token is then in the flow rather than nicely secured away in your n8n authentications - i.e. be careful about what you share as you could then expose your token.
