HaloPSA Complete icon

HaloPSA Complete

Get data from the HaloPSA API

Actions68

Overview

This node integrates with the HaloPSA API to create a new Asset record. It is designed for IT service management and asset tracking scenarios where users need to programmatically add assets into their HaloPSA system. Typical use cases include onboarding new hardware or software assets, registering client-owned equipment, or automating asset inventory updates.

For example, an IT administrator could use this node in an automation workflow to create asset entries when new devices are purchased or assigned to clients, ensuring accurate and up-to-date asset records without manual data entry.

Properties

Name Meaning
Asset Type ID The numeric identifier of the asset type to assign to the new asset.
Client ID The numeric identifier of the client who owns the asset.
Site ID (Optional) The numeric identifier of the site where the asset is located.
Additional Fields A collection of optional fields to provide more details about the asset:
- Business Owner ID Numeric user ID of the business owner responsible for the asset.
- Contract ID Numeric ID of the contract associated with the asset.
- Contract Ref Reference string for the contract.
- Criticality Numeric level indicating how critical the asset is.
- Device Number Numeric device number, defaulting to 1.
- Inactive Boolean flag indicating if the asset is inactive.
- Inventory Number String representing the inventory number.
- Is Template Boolean flag indicating if the asset is a template.
- Item ID Numeric item ID from inventory.
- Key Field Primary key field value as a string.
- Key Field 2 Secondary key field value as a string.
- Key Field 3 Tertiary key field value as a string.
- Notes Text notes about the asset.
- Priority ID Numeric priority identifier for the asset.
- SLA ID Numeric Service Level Agreement ID.
- Status ID Numeric status identifier of the asset.
- Supplier Contract ID Numeric ID of the supplier contract.
- Supplier ID Numeric supplier identifier.
- Technical Owner ID Numeric user ID of the technical owner.
- Third Party ID Numeric ID for third party integration.
- Use Option to specify the use type of the asset: "Asset" or "Configuration Item".
- User ID Numeric user ID assigned to the asset.

Output

The node outputs JSON data representing the newly created asset as returned by the HaloPSA API. This typically includes all the asset's properties such as its unique ID, type, ownership, status, and any additional metadata provided during creation.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the HaloPSA API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node relies on the internal router mechanism to dispatch the create asset request to the appropriate API endpoint.

Troubleshooting

  • Authentication Errors: If the API key or token is invalid or missing, the node will fail to authenticate. Ensure that the correct API credentials are configured in n8n.
  • Validation Errors: Missing required fields like Asset Type ID or Client ID will cause the API to reject the request. Verify that all mandatory inputs are provided.
  • API Connectivity Issues: Network problems or incorrect API URLs can prevent communication. Check network access and API endpoint configuration.
  • Unexpected API Responses: If the API changes or returns errors, review the error message for clues and update the node or credentials accordingly.

Links and References

Discussion