Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Workdays → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Workdays resource and the Post Undefined operation, it allows sending a complex JSON payload representing workday schedules, holidays, timeslots, breaks, and access control configurations.

Typical use cases include automating the management of work schedules, defining holiday periods, setting up time slots for appointments or shifts, and configuring access controls within an organization’s PSA system. For example, you might use this node to programmatically update holiday schedules or define new workday patterns in bulk based on external data sources.

Properties

Name Meaning
Body A JSON object containing detailed configuration for workdays. This includes arrays of holidays (with nested schedule plans and events), timeslots, access control settings, and breaks. The structure supports deeply nested entities such as agents, teams, departments, roles, notifications, custom fields, and many other related sub-objects. Users provide this JSON to define or update workday-related data in Halo PSA.

The property expects a JSON input that can be parsed and sent directly as the request body.

Output

The node outputs the JSON response returned by the Halo PSA API after performing the POST request. The output is structured as:

{
  "json": { /* API response object */ },
  "pairedItem": { "item": <index> }
}
  • json: Contains the full response from the API call, which typically reflects the created or updated workday data.
  • pairedItem: Links the output to the corresponding input item index.

There is no binary data output for 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 POST requests with JSON bodies.
  • No additional environment variables are required beyond the configured API credentials.

Troubleshooting

  • No credentials returned!: Ensure that valid API credentials are configured in n8n before executing the node.
  • Resource or Operation not found: Verify that the resource is set to "Workdays" and the operation matches exactly; otherwise, the node will throw errors.
  • Invalid JSON in Body: The Body property must contain valid JSON. Malformed JSON will cause parsing errors.
  • API Errors: If the API returns errors (e.g., validation errors), these will be included in the node output under the error field if "Continue On Fail" is enabled. Otherwise, the node execution will stop with an error.
  • Large Payloads: Given the complexity and size of the JSON body, ensure the payload does not exceed API limits or timeout constraints.

Links and References

Discussion