Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Mail Campaign → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the "Mail Campaign" resource with the "Post Undefined" operation, it sends a POST request containing a complex JSON body representing a mail campaign's data structure. This can be used to create or update mail campaigns in Halo PSA, including detailed configurations such as recipients, settings, tracking, and related entities.

Common scenarios include automating the creation or updating of email marketing campaigns within Halo PSA from workflows, syncing campaign data, or triggering campaign-related actions programmatically.

Example use cases:

  • Automatically creating a new mail campaign based on external triggers.
  • Updating campaign details dynamically during a workflow.
  • Integrating Halo PSA mail campaigns with other marketing tools or CRMs.

Properties

Name Meaning
Body A JSON object representing the full mail campaign data. It includes nested structures for external links, Mailchimp campaign settings (recipients, segment options, variate settings, tracking, RSS options, social cards, report summaries, delivery status), sent-to lists, emails design, marketing unsubscribes, click and open statistics, and many other detailed campaign-related fields. The property expects a valid JSON string that will be parsed and sent as the request body.

Output

The node outputs an array of items where each item contains a json field holding the response from the Halo PSA API after posting the mail campaign data. The structure of this JSON corresponds to the API's response for the mail campaign endpoint, which typically includes confirmation of the created or updated campaign, its identifiers, and any additional metadata returned by the server.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • Needs configuration of base URL, tenant ID, client ID, and client secret for the Halo PSA service.
  • Uses HTTP requests with appropriate headers for authentication and content type.
  • The node depends on n8n's helper methods for making authenticated requests and parsing input parameters.

Troubleshooting

  • No credentials returned!: Ensure that the API key credential for Halo PSA is properly configured and connected in n8n.
  • Resource or Operation not found: Verify that the resource name ("Mail Campaign") and operation ("Post Undefined") are correctly specified and supported by the node.
  • Invalid JSON in Body: The "Body" property must contain valid JSON. Malformed JSON will cause parsing errors before sending the request.
  • API request failures: Network issues, incorrect authentication details, or invalid payloads may cause errors. Check the error message returned in the node output for specifics.
  • If the node is set to continue on fail, errors will be included in the output JSON under an error field; otherwise, the workflow will stop on error.

Links and References

Discussion