Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation retrieves a list of custom fields associated with suppliers in an account. It is useful when you need to dynamically access or display additional metadata fields that have been customized for supplier records. For example, if your system tracks extra attributes like supplier certifications, preferred payment terms, or regional classifications as custom fields, this operation allows you to fetch all those custom field definitions for further processing or display.

Properties

Name Meaning
Account Id Identifier of the account whose supplier custom fields you want to retrieve

Output

The output JSON contains the list of custom fields defined for suppliers within the specified account. Each item in the list typically includes details such as the custom field's name, type, and possibly other metadata describing the field. This enables downstream nodes or workflows to understand what custom data is available for suppliers.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests.
  • The node interacts with an external API endpoint (base URL provided via credentials) to fetch supplier custom fields.
  • Proper network connectivity to the external service is necessary.

Troubleshooting

  • Missing or invalid Account Id: Ensure the "Account Id" property is correctly set and corresponds to a valid account in the external system.
  • Authentication errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions to read supplier custom fields.
  • Network issues: Check internet connectivity and firewall settings that might block access to the external API.
  • Empty results: If no custom fields are returned, confirm that custom fields exist for suppliers in the specified account.

Links and References

  • Refer to the external API documentation for supplier custom fields to understand the structure and usage of these fields.
  • Consult n8n documentation on how to configure API key credentials and handle HTTP request nodes.

Discussion