Actions68
- Client Actions
- Agent Actions
- Asset Actions
- Field Info Actions
- Invoice Actions
- Site Actions
- Ticket Actions
- Ticket Status Actions
- Ticket Type Actions
- Timesheet Actions
- Timesheet Event Actions
- Webhook Actions
- Webhook Event Actions
Overview
This node integrates with the HaloPSA API to create a new client record. It is useful in scenarios where you want to automate client management by programmatically adding clients into the HaloPSA system from workflows, such as onboarding new customers or syncing client data from other systems.
For example, you could use this node to:
- Automatically add a new client when a form is submitted on your website.
- Sync client information from a CRM system into HaloPSA.
- Create clients in bulk from a spreadsheet or database.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the client to be created (required). |
| Additional Fields | Optional extra fields for the client: |
| - Colour | Color code for the client (e.g., #E83C4A). |
| - Inactive | Boolean flag indicating whether the client is inactive. |
| - Notes | Notes about the client (multi-line text). |
| - Top Level ID | Numeric top level ID associated with the client (default is 1). |
Output
The node outputs JSON data representing the newly created client object as returned by the HaloPSA API. This typically includes the client's unique identifier and all properties set during creation.
If the API supports it, binary data output is not indicated for this operation.
Dependencies
- Requires an active connection to the HaloPSA API using an API key or token configured in n8n credentials.
- The node depends on the HaloPSA API being accessible and the user having permissions to create clients.
- No additional external dependencies are required beyond the API access.
Troubleshooting
Common issues:
- Authentication errors if the API key/token is missing or invalid.
- Validation errors if required fields like "Name" are missing or improperly formatted.
- Network connectivity problems preventing access to the HaloPSA API.
Error messages:
- 401 Unauthorized: Check that the API credential is correctly configured and has sufficient permissions.
- 400 Bad Request: Verify that all required fields are provided and valid, especially the client name.
- Network errors: Ensure the n8n instance can reach the HaloPSA API endpoint.
Resolving these usually involves verifying credentials, input data correctness, and network connectivity.
Links and References
- HaloPSA API Documentation (for detailed API endpoints and data models)
- n8n documentation on creating custom nodes