What is up with the HaloPSA node?

Questions
1

HaloPSA limited functionality

No errors, no options either

My workflow:

Share the output returned by the last node

I can’t. It’s 5200 lines long and irrelevant to this question. The node works, as far as it goes.

The whole point here is I can only submit a ticket as the user for the API key. So, in this case, a ticket created is from “automation”. I want to assign it to the client the computer is from. I’d also like to assign the user of the computer.

Information on your n8n setup

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

hello @russellkg

If the HaloPSA node can’t update a client or a user in the ticket, then try to use the HTTP Request node to do so in the way you need.

You can use the credentials from the HaloPSA node, but you will need to build the body by yourself.

3

That would be all well and good, except sending an http request results in errors which don’t even make sense to HaloPSA support.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.