Do the HaloPSA credentials work with the http request node?

[russellkg]

Describe the problem/error/question

I’m doing a lot with assets in HaloPSA. Assets are one area of HaloPSA that isn’t handled at all in the HaloPSA node.

For these instances, the docs say to use credentials with the http node. The problem is, the http node does not list HaloPSA in the credentials field.

What is the error message (if any)?

No error message, it’s just not there. I did check the node version number. It’s version 4.2.

Please share your workflow

I can do so, but this is not workflow related.

Share the output returned by the last node

Also not relevant.

Information on your n8n setup

• n8n version: 1.84.1
• Database (default: SQLite): PostgresQL 15
• n8n EXECUTIONS_PROCESS setting (default: own, main): default
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker on Digital Ocean.
• Operating system: Ubuntu 22.04

[n8nMacGyver]

You just need to use one of the Generic Credential Types.

So instead of selecting ‘Predefined Credential Type’, select ‘Generic Credential Type’, and then choose the option that matches your authentication choice.

You can learn more about the generic types here:

HTTP Request credentials | n8n Docs

[russellkg]

Yeah, I have that working. I was wondering about the Halo credentials because they have a bearer token that expires in an hour.

I have a workflow that checks the bearer I have and if it’s over the expire time, it gets a new one, but this is a process and I’m pretty sure I’m inefficient. E.g. I’m sure it is checking the bearer for each client I’m processing, even though there’s only one tenant involved here.

Thanks for the information. Maybe a note on those that don’t support the http node would be a good thing. It would have save me a few minutes.

Have a good weekend.

-Russ