Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node allows you to create webhook subscriptions for specific event types related to an account. By setting up a webhook subscription, you can receive real-time notifications via HTTP callbacks whenever certain events occur, such as expense creation, payment authorization, or supplier updates. This is useful for automating workflows that depend on external system events, like triggering downstream processes, updating databases, or sending alerts.

Practical examples:

  • Automatically update your internal expense tracking system when a new expense is created.
  • Trigger a notification workflow when a payment fails.
  • Sync supplier information in your CRM when a supplier is created or updated.

Properties

Name Meaning
Account Id Identifier of the account for which the webhook subscription is being created.
Event Type The 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 event notifications will be sent. Must be a valid callback endpoint.

Output

The node outputs JSON data representing the created webhook subscription. This typically includes details such as the subscription ID, the subscribed event type, the callback URL, and possibly metadata about the subscription status.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the external service managing webhook subscriptions.
  • The node expects a base URL configured in credentials to send requests to the appropriate API endpoint.
  • The callback URL must be accessible over HTTPS to receive webhook calls.

Troubleshooting

  • Invalid Callback URL: If the callback URL is not a valid HTTPS URI, the API may reject the subscription request. Ensure the URL starts with https:// and is reachable.
  • Authentication Errors: Missing or invalid API authentication tokens will cause failures. Verify that the API key credential is correctly set up.
  • Event Type Not Supported: Selecting an unsupported event type will result in errors. Use only the provided event options.
  • Network Issues: Connectivity problems between n8n and the API endpoint or callback URL can cause timeouts or failed webhook delivery.
  • Duplicate Subscriptions: Creating multiple subscriptions for the same event and callback URL might be disallowed or cause unexpected behavior.

Links and References

Discussion