Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Custom Table → Post 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 Custom Table resource and the Post Undefined operation, it sends a POST request with a complex JSON body to create or update custom table data in Halo PSA.

Typical use cases include automating the management of custom tables in Halo PSA, such as adding or editing custom fields, managing validation rules, access controls, and other metadata related to custom tables. This is useful for organizations that need to programmatically maintain their PSA configurations or synchronize data from other systems.

Example scenarios:

  • Automatically updating custom table definitions based on external configuration files.
  • Creating new entries in custom tables as part of a larger workflow automation.
  • Managing access control and validation rules dynamically via n8n workflows.

Properties

Name Meaning
Body A JSON object representing the full structure of the custom table data to be posted. It includes nested arrays and objects for ctfield, customfields, add_customfields, edit_customfields, delete_customfields, fields (with sub-properties like defaultvalue_table, values, table_values, table_info, etc.), and access_control. The user must provide this JSON structure according to the Halo PSA API's expected schema for custom tables.

The property expects a JSON input that can be quite complex, reflecting the detailed structure of custom tables in Halo PSA.

Output

The node outputs the JSON response returned by the Halo PSA API after posting the custom table data. The output is structured as:

{
  "json": { /* API response object */ }
}

The exact structure depends on the API response but typically includes confirmation of the created or updated custom table, any errors, or status messages.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Halo PSA API.
  • Needs credentials including base URL, tenant identifier, client ID, and client secret for authentication.
  • The node uses HTTP requests with appropriate headers (X-Tenant, X-HaloPSA-ClientId, X-HaloPSA-ClientSecret) to authenticate.
  • No additional external dependencies beyond the configured API credentials.

Troubleshooting

  • Missing Credentials Error: If no credentials are provided or they are invalid, the node will throw an error "No credentials returned!". Ensure that valid API credentials are configured in n8n.
  • Resource or Operation Not Found: Errors like "Resource Custom Table not found" or "Operation Post Undefined not found for resource Custom Table" indicate misconfiguration of resource or operation names.
  • Invalid JSON Body: Since the body is parsed from JSON, malformed JSON input will cause parsing errors. Validate the JSON before running the node.
  • API Request Failures: Network issues, incorrect endpoint URLs, or authentication failures will result in HTTP errors. Check the base URL and credentials.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion