Actions27
- Accounting Export Actions
- Contract Actions
- Customer Actions
- Invoice Actions
- Metered Usage Actions
- Order Actions
- Payment Actions
- Report Actions
Overview
The Billwerk n8n node allows you to automate interactions with the Billwerk subscription management platform. Specifically, when using the Customer resource and the Get operation, this node retrieves information about a specific customer from your Billwerk account based on their unique Customer ID.
Common scenarios:
- Fetching customer details for use in automated workflows (e.g., support ticket enrichment, CRM updates).
- Validating customer existence before performing further actions.
- Integrating Billwerk customer data with other business tools.
Practical example:
You could use this node to automatically retrieve a customer's profile when a new order is placed, then pass that data to another system or send a notification.
Properties
| Name | Type | Meaning |
|---|---|---|
| Customer ID | String | The unique identifier of the customer whose information you want to retrieve from Billwerk. |
Output
The output will be a JSON object containing the details of the requested customer. The exact structure depends on the Billwerk API response, but typically includes fields such as customer name, contact information, status, and other relevant attributes.
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
billwerkApicredential in n8n for authentication.
Troubleshooting
Common issues:
- Invalid Customer ID: If the provided Customer ID does not exist, the node may return an error indicating the customer was not found.
- Authentication errors: If the Billwerk API credentials are missing or incorrect, you may see authentication/authorization errors.
- API rate limits: Excessive requests may trigger rate limiting by Billwerk.
Error handling:
- If "Continue On Fail" is enabled, errors are returned in the output as
{ "error": "Error message" }. - Otherwise, the workflow execution will stop on error.