Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation allows users to create webhook subscriptions for various event types related to an account. By setting up a webhook subscription, the user can receive real-time notifications via a callback URL whenever specific events occur, such as expense creation, payment authorization, or supplier updates. This is particularly useful for automating workflows that depend on external system events, like triggering downstream processes when an expense is approved or a payment fails.
Practical examples:
- Automatically update your internal accounting system when a new expense is created.
- Notify your finance team via Slack when a payment is authorized or reverted.
- Trigger document processing workflows when an expense document is uploaded.
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 HTTPS URI. |
Output
The node outputs JSON data representing the response from the API after creating the webhook subscription. This typically includes details about the newly created subscription such as its unique identifier, subscribed event type, associated account, and the callback URL registered.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing webhook subscriptions.
- The node expects the base URL of the API to be configured in the credentials.
- 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 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 the request to fail. Verify that the API key credential is correctly set up.
- Event Type Not Supported: Selecting an unsupported event type will result in an error. Use one of the predefined event options.
- Network Issues: Connectivity problems between n8n and the API endpoint can cause timeouts or failures. Check network settings and firewall rules.
- Duplicate Subscriptions: Attempting to create a subscription for the same event and callback URL multiple times might be rejected or cause unexpected behavior.
Links and References
- Webhook Concepts and Best Practices
- API Documentation for Webhook Subscriptions (generic) (Replace with actual API docs if available)