Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.
```
<your workflow>
```
That implies to any JSON output you would like to share with us.
Make sure that you have removed any sensitive information from your workflow and include dummy or pinned data with it!
We are aware of the missing required fields and have an internal ticket to have it fixed. However, the HaloPSA documentation is not clear and does not indicate which field is required. There are literally hundreds fields that could be added to the payload.
Could you let us know what fields are required for your use case (create client)?
Also, meanwhile you could use generic HTTP Request node to utilize HaloPSA API.
currently when trying to run it errors trying to make the “main contact name” are you able to add that field and ill run a test again to see if yells for the next thing
Unfortunately I have no access to HaloPSA. As I mentioned you can use HTTP Request node composing the payload yourself and adding a property one by one. This way you can determine which field is required.
I cannot be sure that all the fields in your last post is actually mandatory to be able to create a client.
If you self-host the instance and you have skills for managing Node.js and Typescript projects you could make changes yourself. Though, I believe you can overcome the issue by utilizing generic HTTP Request node to communicate with HaloPSA API, no need to wait for a fix if the matter is urgent.