Billwerk

Automate your subscription business with billwerk

Actions27

Accounting Export Actions
- Get Download Link
Contract Actions
Customer Actions
Invoice Actions
Metered Usage Actions
Order Actions
Payment Actions
Report Actions
- Get Download Link

Overview

The Billwerk node for n8n automates operations related to subscription business management using the Billwerk API.
For the Order → Commit operation, this node finalizes or "commits" an order in your Billwerk system, typically marking it as processed or completed.
This is useful in workflows where you need to programmatically confirm orders after certain checks or steps, such as after payment confirmation or manual review.

Example scenarios:

Automatically commit an order after a successful payment.
Batch process and commit multiple pending orders at scheduled intervals.
Integrate with other systems (e.g., CRM, ERP) to finalize orders based on external triggers.

Properties

Name	Type	Meaning
Order ID	String	The unique identifier of the order to be committed. This tells the node which order to finalize in Billwerk.

Output

The output will be a JSON object representing the result of the commit operation for the specified order.
While the exact structure depends on the Billwerk API response, you can expect fields such as:

{
  "id": "string",           // The committed order's ID
  "status": "string",       // New status after commit (e.g., "committed")
  "message": "string",      // Any informational message from the API
  ...                      // Additional order details as returned by Billwerk
}

If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message.

Dependencies

External Service: Requires access to the Billwerk API.
Credentials: You must configure the billwerkApi credential in n8n for authentication.

Troubleshooting

Common Issues:

Invalid Order ID: If the provided Order ID does not exist or is incorrect, the node will return an error message indicating the order was not found.
Missing Credentials: If the billwerkApi credential is not set up, the node will fail to authenticate.
API Errors: Any issues from the Billwerk API (such as permission errors or invalid state transitions) will be surfaced as error messages.

Error Handling:

If "Continue On Fail" is enabled, failed items will output an object with an error property containing the error message.
Otherwise, the workflow will stop on the first encountered error.