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 enables automation of subscription business processes by integrating with the Billwerk platform. Specifically, when using the Customer resource and the Delete operation, this node allows you to delete a customer from your Billwerk account. This is useful in scenarios where you need to automate customer data management, such as removing customers who have canceled their subscriptions or are no longer active.
Practical Example:
- Automatically remove a customer record in Billwerk when they unsubscribe via another system integrated with n8n.
Properties
| Name | Type | Meaning |
|---|---|---|
| Customer ID | String | The unique identifier of the customer to be deleted. Required to specify which customer to remove from Billwerk. |
Output
The output will be a JSON object (or array of objects) representing the result of the delete operation. Typically, this may include:
- Confirmation of deletion (e.g., status, message)
- The ID of the deleted customer
- Any error messages if the operation failed
If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message.
Example Output:
[
{
"id": "customer_12345",
"status": "deleted"
}
]
Or, on failure (with continue on fail):
[
{
"error": "Customer not found"
}
]
Dependencies
- External Service: Requires access to the Billwerk API.
- Credentials: You must configure the
billwerkApicredential in n8n for authentication. - n8n Configuration: No additional environment variables are required beyond standard credential setup.
Troubleshooting
Common Issues:
- Invalid Customer ID: If the provided Customer ID does not exist, the node will return an error message such as
"Customer not found". - Authentication Errors: If the Billwerk API credentials are missing or incorrect, the node will throw an authentication error.
- API Rate Limits: Excessive requests may lead to rate limiting by Billwerk.
- Invalid Customer ID: If the provided Customer ID does not exist, the node will return an error message such as
Error Handling:
- If "Continue On Fail" is enabled, errors will be included in the output under the
errorfield, allowing workflows to proceed. - Without "Continue On Fail", the workflow will stop on the first encountered error.
- If "Continue On Fail" is enabled, errors will be included in the output under the