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 API. Specifically, when configured with the Order resource and the Approve operation, this node allows users to approve an order in their Billwerk account. This is useful in workflows where orders need to be programmatically approved after certain conditions are met, such as after payment confirmation or manual review.
Practical Example:
- Automatically approve customer orders once a payment has been successfully processed.
- Integrate with other systems (e.g., CRM, ERP) to trigger order approval based on external events.
Properties
| Name | Type | Meaning |
|---|---|---|
| Order ID | String | The unique identifier of the order you want to approve. Required to specify the target order for the approval action. |
Output
The output will be a JSON object representing the result of the order approval operation. The structure typically includes details about the approved order, such as its status, ID, and possibly additional metadata returned by the Billwerk API.
Example Output:
{
"id": "order_12345",
"status": "approved",
"customerId": "cust_67890",
// ...other order fields
}
If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message:
{
"error": "Order not found"
}
Dependencies
- External Service: Requires access to the Billwerk API.
- API Credentials: You must configure the
billwerkApicredential in n8n for authentication. - n8n Configuration: No special environment variables required beyond standard credential setup.
Troubleshooting
Common Issues:
- Invalid Order ID: If the provided Order ID does not exist, the node will return an error message like
"Order not found". - Authentication Errors: If the Billwerk API credentials are missing or incorrect, you may see errors related to authentication failure.
- Insufficient Permissions: The API user may lack permission to approve orders, resulting in authorization errors.
Error Handling:
- If "Continue On Fail" is enabled, errors are returned in the output as an
errorfield. - If not enabled, the workflow will stop on error.