Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node allows users to create webhook subscriptions for various event types related to an account. By setting up a webhook subscription, the node enables real-time notifications to be sent to a specified callback URL whenever certain events occur, such as expense creation, payment authorization, or supplier updates. This is useful in scenarios where you want to automate workflows triggered by these events, like updating internal systems, sending alerts, or syncing data.

For example, you could use this node to subscribe to "Expense Created" events so that every time a new expense is recorded, your system receives a notification and can process it automatically.

Properties

Name Meaning
Account Id Identifier of the account for which the webhook subscription is created.
Event Type Type of event to subscribe to. Options include: Expense Created, Expense Reviewed, Expense Approved, Expense Deleted, Expense Payment Details Updated, Expense Document Uploaded, Payment Authorized, Payment Reverted, Payment Settled, Payment Failed, Deposit Received, Supplier Created, Supplier Updated, Purchase Order Status Changed.
Callback Url The HTTPS URL where webhook notifications will be sent when the subscribed event occurs.

Output

The node outputs JSON data representing the response from the webhook subscription creation API call. This typically includes details about the newly created webhook subscription such as its identifier, status, and configuration. The output does not include binary data.

Dependencies

  • Requires an API key credential for authenticating with the external service managing webhook subscriptions.
  • The node expects the base URL and authentication credentials to be configured properly in n8n.
  • The callback URL must be a valid HTTPS endpoint capable of receiving POST requests.

Troubleshooting

  • Invalid Callback URL: If the callback URL is not a valid HTTPS URI, the subscription creation will fail. Ensure the URL starts with https:// and is reachable.
  • Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key or token is correctly set up in n8n credentials.
  • Unsupported Event Type: Selecting an event type not supported by the API will result in errors. Use only the provided event options.
  • Network Issues: Connectivity problems between n8n and the external API or callback URL can cause timeouts or failures. Check network access and firewall settings.

Links and References

  • Webhook Concepts – General information on webhooks.
  • Documentation for the external API managing webhook subscriptions (not provided here).

Discussion