HaloPSA Complete icon

HaloPSA Complete

Get data from the HaloPSA API

Actions68

Overview

This node integrates with the HaloPSA API to update an existing asset's details. It is designed for scenarios where you need to modify asset information such as ownership, status, location, or other metadata within your IT service management system. For example, you might use this node to update the business owner of an asset after a team reorganization, change the asset's status when it is decommissioned, or adjust priority levels based on new operational requirements.

Properties

Name Meaning
Asset ID The unique identifier of the asset to update (required).
Update Fields A collection of fields to update on the asset. Possible fields include:
- Asset Type ID: Numeric ID representing the type of asset.
- Business Owner ID: User ID of the business owner.
- Client ID: ID of the client owning the asset.
- Contract ID: Associated contract's ID.
- Contract Ref: Reference string for the contract.
- Criticality: Numeric level indicating asset criticality.
- Device Number: Numeric device number.
- Inactive: Boolean flag indicating if the asset is inactive.
- Inventory Number: String inventory number.
- Is Template: Boolean flag indicating if the asset is a template.
- Item ID: Inventory item ID.
- Key Field, Key Field 2, Key Field 3: Primary, secondary, and tertiary key field values.
- Notes: Text notes about the asset.
- Priority ID: Numeric priority level.
- Site ID: Location/site ID where the asset is located.
- SLA ID: Service Level Agreement ID.
- Status ID: Current status ID of the asset.
- Supplier Contract ID: Supplier contract ID.
- Supplier ID: Supplier ID.
- Technical Owner ID: User ID of the technical owner.
- Third Party ID: ID for third party integration.
- Use: Option to specify the asset use type, either "Asset" or "Configuration Item".
- User ID: User ID assigned to the asset.

Output

The node outputs JSON data representing the updated asset object as returned by the HaloPSA API. This typically includes all asset properties reflecting the changes made. The output does not include binary data.

Dependencies

  • Requires an API key credential for authenticating with the HaloPSA API.
  • The node depends on the HaloPSA API being accessible and properly configured.
  • No additional external dependencies are required beyond the API access.

Troubleshooting

  • Common Issues:

    • Invalid or missing Asset ID will cause the update to fail.
    • Providing invalid field values (e.g., non-numeric where numeric expected) may result in API errors.
    • Network connectivity issues can prevent communication with the HaloPSA API.
    • Insufficient permissions associated with the API key may block updates.

  • Error Messages:

    • "Asset not found": Verify that the Asset ID exists in the HaloPSA system.
    • "Unauthorized" or "Authentication failed": Check that the API key credential is valid and has necessary permissions.
    • "Invalid input": Review the fields provided in Update Fields for correct types and valid values.

Resolving these usually involves verifying input parameters, ensuring correct credentials, and confirming network connectivity.

Links and References

Discussion