Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Outgoing → 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 "Outgoing" resource and the "Post Undefined" operation, it sends a POST request with a JSON-parsed body derived from the input data.

Common scenarios include automating the creation or sending of outgoing messages or records in Halo PSA by providing structured data as input. For example, a user might automate ticket updates, notifications, or other outbound communications by passing JSON-formatted content to this node.

Properties

Name Meaning
Body A numeric input that is parsed as JSON and sent as the request body. The property expects a stringified JSON value which will be parsed before sending.

Note: Although the property type is number in the definition, the routing configuration indicates that its value is parsed as JSON (JSON.parse($value)), implying the input should be a JSON string representing the body content.

Output

  • The node outputs an array of items where each item contains a json field.
  • The json field holds the response returned by the Halo PSA API after performing the POST request.
  • If the request fails and the node is configured to continue on failure, the output will contain an error message inside the json.error field.
  • No binary data output is produced by this node.

Dependencies

  • Requires valid credentials for the Halo PSA API, including:
    • Base URL
    • Tenant identifier
    • Client ID
    • Client Secret
  • These credentials must be configured in n8n prior to using the node.
  • The node uses HTTP requests to communicate with the Halo PSA API endpoints.

Troubleshooting

  • No credentials returned!
    This error occurs if the node cannot retrieve the required API credentials. Ensure that the API key credential is properly set up and assigned to the node.

  • Resource or Operation not found
    If the specified resource or operation does not exist in the node's configuration, verify that the correct resource and operation names are selected.

  • JSON parsing errors
    Since the "Body" property expects a JSON string that is parsed before sending, invalid JSON input will cause errors. Make sure the input is a valid JSON string.

  • API request failures
    Network issues, incorrect credentials, or invalid request bodies can cause the API call to fail. Check the error message returned in the output and verify the request parameters and credentials.

Links and References

Note: The node dynamically constructs the API endpoint and method based on the selected resource and operation. For the "Outgoing" resource with "Post Undefined" operation, it performs a POST request with a JSON body parsed from the "Body" property.

Discussion