Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node is designed to retrieve the workflow status of a specific expense within an account. It is useful in scenarios where users need to track or monitor the current state of an expense's approval or processing workflow. For example, finance teams can use this node to check if an expense has been approved, rejected, or is still pending, enabling automated follow-ups or reporting.

Properties

Name Meaning
Account Id Identifier of the account containing the expense. This is required to specify the context for the expense.
Expense Id Identifier of the specific expense whose workflow status is being requested. This is required to pinpoint the exact expense.

Output

The node outputs JSON data representing the workflow status of the specified expense. The structure typically includes details such as the current state of the expense in its approval process, timestamps, and possibly metadata about the workflow steps completed or pending.

If the node supports binary data output (not evident from the provided code), it would generally relate to attachments or documents associated with the expense, but no such indication is present here.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the external service managing expenses.
  • Depends on an external API endpoint that provides expense workflow status information.
  • The base URL for API requests is expected to be set in the node’s credentials configuration.

Troubleshooting

  • Missing or invalid Account Id or Expense Id: Ensure both identifiers are correctly provided; otherwise, the API call will fail or return errors.
  • Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to access expense data.
  • Network or API errors: Check connectivity and API availability. Rate limits or service outages may cause failures.
  • Unexpected response format: If the API changes, the node might not parse the response correctly, leading to errors or empty outputs.

Links and References

  • Refer to the external API documentation for detailed information on expense workflow statuses and required parameters.
  • Consult n8n documentation on how to configure API credentials and handle HTTP request nodes for custom integrations.

Discussion