Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Charge Rate → Get One Charge Rate

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information about a specific Charge Rate. It is designed to fetch one Charge Rate by its unique identifier, optionally including additional details if requested.

Common scenarios for this node include:

  • Retrieving billing or pricing information related to services or projects.
  • Accessing charge rate data to calculate costs or generate invoices.
  • Integrating Charge Rate data into workflows that require up-to-date pricing information.

For example, you might use this node in an automation that pulls a Charge Rate by ID and then uses that data to update a financial report or trigger notifications based on pricing changes.

Properties

Name Meaning
Id The unique numeric identifier of the Charge Rate to retrieve.
Includedetails Optional flag to specify whether to include additional details in the response.

Output

The node outputs a JSON object representing the Charge Rate retrieved from the Halo PSA API. This includes all standard fields of the Charge Rate entity, such as its ID, name, rate values, and any other metadata provided by the API.

If the Includedetails property is set, the output may contain extended information related to the Charge Rate.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "id": 123,
  "name": "Standard Hourly Rate",
  "rate": 150,
  "currency": "USD",
  "details": {
    // Additional details if included
  }
}

Dependencies

  • Requires valid credentials for the Halo PSA API, including base URL, tenant identifier, client ID, and client secret.
  • The node depends on network access to the Halo PSA API endpoint.
  • No additional external dependencies beyond the n8n environment and the configured API credentials.

Troubleshooting

  • No credentials returned!
    This error indicates missing or invalid API credentials. Ensure that the required API authentication token or key is properly configured in the node's credentials section.

  • Resource or Operation not found
    If the specified resource ("Charge Rate") or operation ("Get One Charge Rate") is not recognized, verify that the node parameters are correctly set and that the node version supports these options.

  • HTTP request errors
    Network issues, incorrect base URL, or invalid tenant/client credentials can cause request failures. Check connectivity and credential correctness.

  • JSON parsing errors
    If additional query parameters or request bodies are used, ensure they are valid JSON strings when applicable.

Using the "Continue On Fail" option can help handle errors gracefully within workflows.

Links and References

Discussion