Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Field Info → Delete Undefined

AI-generated

Overview

This node integrates with the Halo PSA API, allowing users to perform various operations on different resources within the Halo PSA system. Specifically, for the Field Info resource and the Delete Undefined operation, it enables deleting a field info entry identified by its unique ID.

Common scenarios where this node is beneficial include automating management of custom fields or metadata in Halo PSA, cleaning up undefined or obsolete field entries, and integrating field data maintenance into broader workflows.

For example, a user might automate the removal of undefined field info records that are no longer needed, triggered by certain events or schedules, helping keep the system clean and consistent.

Properties

Name Meaning
Id The numeric identifier of the Field Info entry to delete. This property is required.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains a json field with the response from the Halo PSA API for the delete operation.

  • On success, the json field will contain the API's confirmation or details about the deleted field info.
  • On failure, if "Continue On Fail" is enabled, the json field will contain an error property with the error message.

No binary data output is produced by this operation.

Dependencies

  • Requires valid credentials for the Halo PSA API, including base URL, tenant identifier, client ID, and client secret.
  • The node uses these credentials to authenticate API requests via HTTP headers.
  • No additional external dependencies beyond the Halo PSA API and n8n core modules.

Troubleshooting

  • No credentials returned!: Indicates missing or misconfigured API credentials. Ensure the API key credential is properly set up in n8n.
  • Resource or Operation not found: Occurs if the specified resource or operation name does not match those defined in the node. Verify correct spelling and casing.
  • API request errors: Network issues, invalid IDs, or permission problems can cause API call failures. Check the error message returned in the output JSON for details.
  • If the node is set to continue on fail, errors will be reported per item without stopping the workflow; otherwise, the workflow execution will halt on the first error.

Links and References

Discussion