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 using the Billwerk platform. Specifically, when configured with the Resource: Contract and Operation: Delete, this node allows users to delete a contract from their Billwerk account. This is useful in scenarios where contracts need to be programmatically removed, such as handling customer cancellations, cleaning up test data, or automating contract lifecycle management.
Practical Example:
A company wants to automatically remove expired or cancelled contracts from Billwerk as part of their offboarding workflow. By using this node in an n8n workflow, they can trigger contract deletion based on specific events or schedules.
Properties
| Name | Type | Meaning |
|---|---|---|
| Contract ID | String | The unique identifier of the contract to be deleted. Required to specify which contract to remove from Billwerk. |
Output
- The output will be a JSON object (or array of objects) representing the result of the delete operation.
- If the operation is successful, the output typically contains confirmation details about the deleted contract (such as its ID or status).
- If an error occurs and "Continue On Fail" is enabled, the output will include an
errorfield with the error message.
Example Output:
[
{
"id": "contract_12345",
"status": "deleted"
}
]
Or, in case of error:
[
{
"error": "Contract not found"
}
]
Dependencies
- External Service: Requires access to the Billwerk API.
- Credentials: You must configure the
billwerkApicredential in n8n with valid API keys or authentication details for your Billwerk account.
Troubleshooting
Common Issues:
- Invalid Contract ID: If the provided Contract ID does not exist, the node will return an error such as
"Contract not found". - Authentication Errors: If the Billwerk API credentials are missing or incorrect, you may receive authentication or authorization errors.
- Insufficient Permissions: The API user must have permission to delete contracts; otherwise, the operation will fail.
- Invalid Contract ID: If the provided Contract ID does not exist, the node will return an error such as
Error Handling:
- If "Continue On Fail" is enabled, errors will be included in the output under the
errorfield, allowing workflows to proceed even if some deletions fail. - If not enabled, the workflow will stop on the first encountered error.
- If "Continue On Fail" is enabled, errors will be included in the output under the