Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation retrieves a list of all available expense categories for a specified account. It is useful in scenarios where you need to dynamically fetch and display expense categories from an external financial or accounting system, enabling users to select or filter expenses based on these categories. For example, it can be used in automated workflows that categorize expenses, generate reports, or synchronize expense data with other systems.

Properties

Name Meaning
Account Id Identifier of the account to fetch expense categories from

Output

The output contains a JSON array listing all expense categories associated with the given account. Each item in the array represents an expense category object with its details (such as category name and identifier). This structured data can be used downstream in the workflow for filtering, mapping, or reporting purposes.

No binary data output is produced by this node operation.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the external service.
  • The node interacts with an external API endpoint defined by the base URL set in the credentials.
  • Proper network connectivity to the external service is necessary.

Troubleshooting

  • Missing or invalid Account Id: Ensure the "Account Id" property is provided and correctly references an existing account.
  • Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to read expense categories.
  • Network issues: Check internet connectivity and firewall settings that might block access to the external API.
  • Empty results: If no categories are returned, confirm that the account actually has expense categories defined in the external system.

Links and References

  • Refer to the external service’s API documentation for detailed information about expense categories endpoints.
  • Consult n8n documentation on how to configure API credentials and handle HTTP request nodes.

Discussion