Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Marketing Unsubscribe → 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 Marketing Unsubscribe resource with the Post Undefined operation, it sends a POST request to an endpoint related to marketing unsubscribe functionality. This can be used to programmatically unsubscribe contacts or users from marketing communications.

Common scenarios include:

  • Automatically unsubscribing users based on external triggers or workflows.
  • Managing marketing preferences in bulk by sending JSON payloads describing unsubscribe requests.
  • Integrating Halo PSA marketing unsubscribe features into broader automation pipelines.

Example: A workflow that listens for unsubscribe requests from a web form and uses this node to update the marketing unsubscribe status in Halo PSA.

Properties

Name Meaning
Body JSON object representing the request body sent to the marketing unsubscribe endpoint. Users provide the JSON content that defines the unsubscribe details.

The "Body" property accepts raw JSON input, which is parsed and sent as the HTTP request body.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:

  • json: The parsed JSON response returned by the Halo PSA API after performing the unsubscribe operation.
  • If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message instead.

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, and client secret.
  • The node makes authenticated HTTP requests to the Halo PSA API endpoints.
  • No additional external services are required beyond the Halo PSA API itself.

Troubleshooting

  • No credentials returned!
    This error indicates missing or invalid API credentials. Ensure that the API key credential is properly configured in n8n.

  • Resource or Operation not found
    Occurs if the specified resource or operation does not exist in the node's configuration. Verify that "Marketing Unsubscribe" and "Post Undefined" are correctly selected.

  • JSON parsing errors
    Since the "Body" property expects valid JSON, malformed JSON input will cause failures. Validate JSON syntax before running the node.

  • API request failures
    Network issues, incorrect credentials, or invalid request bodies may cause the API call to fail. Check the error messages returned in the output for details.

  • Enable "Continue On Fail" to allow the workflow to proceed even if some items fail, capturing error messages in the output.

Links and References

Discussion