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 manage "Field Info" data, specifically supporting the creation of new field info entries. It is useful in scenarios where users need to programmatically add custom field information into their HaloPSA system, such as automating the setup of metadata fields for assets, tickets, or clients.
For example, a user might use this node to create a new custom field that tracks additional asset details or ticket attributes, enabling enhanced data capture and reporting within HaloPSA.
Properties
| Name | Meaning |
|---|---|
| Field Info Data | JSON object containing the data for the field info to create. This should include all necessary properties as defined by the HaloPSA API for a field info entry. |
Output
The node outputs the response from the HaloPSA API after creating the field info. The output is structured as JSON and typically contains the details of the newly created field info record, including its ID and any other relevant metadata returned by the API.
If the API supports it, binary data is not expected in this operation; the output is purely JSON-based.
Dependencies
- Requires an active connection to the HaloPSA API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node relies on the internal router mechanism to handle API calls, which abstracts HTTP request details.
Troubleshooting
- Invalid JSON input: If the "Field Info Data" property contains malformed JSON, the node will fail. Ensure the JSON is correctly formatted.
- API authentication errors: Missing or incorrect API credentials will cause authorization failures. Verify that the API key/token is valid and properly configured.
- Validation errors from API: If required fields are missing or invalid in the JSON data, the API may return errors. Consult the HaloPSA API documentation for required fields when creating field info.
- Network issues: Connectivity problems can prevent successful API calls. Check network access and proxy settings if applicable.
Links and References
- HaloPSA API Documentation (general reference for API endpoints and data formats)
- n8n Documentation on Creating Custom Nodes