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 automates operations related to subscription business management using the Billwerk platform.
For the resource Contract and operation End, this node allows you to end (cancel) an existing contract as of a specified date.
Common scenarios:
- Automating the cancellation of customer contracts at a scheduled time.
- Integrating contract termination into larger workflows, such as offboarding or billing adjustments.
- Ensuring compliance by programmatically ending contracts on specific dates.
Example use case:
A company wants to automatically end a customer's subscription contract on their requested cancellation date, updating both internal systems and Billwerk records.
Properties
| Name | Type | Meaning |
|---|---|---|
| Contract ID | String | The unique identifier of the contract to be ended. |
| End Date | DateTime | The date when the contract should be cancelled/terminated. |
Output
The output is a JSON object representing the result of the contract end operation.
Typical fields may include:
- Confirmation of the contract's end status.
- The contract ID.
- The effective end date.
- Any error messages if the operation failed.
If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message.
Dependencies
- External Service: Requires access to the Billwerk API.
- Credentials: You must configure the
billwerkApicredential in n8n for authentication.
Troubleshooting
Common issues:
- Invalid Contract ID: If the provided Contract ID does not exist, the node will return an error.
- Missing End Date: If no end date is provided, the API may reject the request.
- Authentication Errors: Incorrect or missing API credentials will prevent successful execution.
Error handling:
- If "Continue On Fail" is enabled, errors are returned in the output as
{ "error": "error message" }. - Otherwise, the workflow will stop on error.