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 API. Specifically, when using the Payment resource and the Get operation, this node retrieves details about a specific payment transaction based on its unique ID. This is useful in scenarios where you need to fetch payment information for reconciliation, reporting, or follow-up actions within your automated workflows.
Practical examples:
- Retrieve payment details after a customer completes a transaction.
- Automatically check the status of a payment before provisioning services.
- Fetch payment data for integration with accounting or CRM systems.
Properties
| Name | Type | Meaning |
|---|---|---|
| Payment Transaction ID | String | The unique identifier of the payment transaction you want to retrieve from Billwerk. |
Output
The output will be a JSON object containing the details of the requested payment transaction. The exact structure depends on the Billwerk API response, but typically includes fields such as:
{
"id": "string",
"amount": "number",
"currency": "string",
"status": "string",
"createdAt": "string (ISO date)",
// ...other payment-related fields
}
If an error occurs and "Continue On Fail" is enabled, the output may include:
{
"error": "Error message string"
}
Dependencies
- External Service: Requires access to the Billwerk API.
- Credentials: You must configure the
billwerkApicredential in n8n with appropriate API keys or authentication details.
Troubleshooting
Common issues:
- Invalid Payment Transaction ID: If the provided ID does not exist, the node will return an error message indicating that the payment was not found.
- Authentication Errors: If credentials are missing or incorrect, you may receive authentication or authorization errors from the Billwerk API.
- Network Issues: Connectivity problems can result in timeout or network error messages.
Error handling:
- If "Continue On Fail" is enabled, errors are returned in the output as an
errorfield in the JSON. - Otherwise, the workflow execution will stop on error.