Actions27
- Accounting Export Actions
- Contract Actions
- Customer Actions
- Invoice Actions
- Metered Usage Actions
- Order Actions
- Payment Actions
- Report Actions
Overview
The Billwerk node for n8n allows you to automate operations related to subscription business management using the Billwerk API.
For the Order resource with the Delete operation, this node enables you to delete an existing order in your Billwerk account by specifying its Order ID.
Common scenarios:
- Removing test or erroneous orders from your Billwerk system.
- Automating cleanup of outdated or cancelled orders as part of a workflow.
- Integrating order deletion into larger automation processes (e.g., after customer cancellation).
Example use case:
When a customer cancels their subscription and you want to ensure all associated orders are removed from Billwerk automatically.
Properties
| Name | Type | Meaning |
|---|---|---|
| Order ID | String | The unique identifier of the order you wish to delete from Billwerk. |
Output
The output will be a JSON object representing the result of the delete operation. Typically, it may include:
- Confirmation of successful deletion (such as a status message or deleted order details).
- If an error occurs and "Continue On Fail" is enabled, the output will contain an
errorfield with the error message.
Example output:
[
{
"status": "success",
"message": "Order deleted successfully"
}
]
or, on failure (with Continue On Fail):
[
{
"error": "Order not found"
}
]
Dependencies
- External Service: Requires access to the Billwerk API.
- API Key/Credentials: You must configure the
billwerkApicredentials in n8n for authentication.
Troubleshooting
Common issues:
- Invalid Order ID: If the provided Order ID does not exist, you may receive an error such as
"Order not found". - Authentication errors: If the Billwerk API credentials are missing or incorrect, the node will fail to connect.
- Insufficient permissions: The API key used must have permission to delete orders.
Error handling:
- If "Continue On Fail" is enabled, errors will be returned in the output as an
errorfield instead of stopping the workflow. - Otherwise, the workflow will stop on the first encountered error.