Billwerk icon

Billwerk

Automate your subscription business with billwerk

Actions27

Overview

The Billwerk node for n8n automates interactions with the Billwerk subscription management platform. Specifically, when configured with the Order resource and the Get operation, this node retrieves detailed information about a specific order from your Billwerk account using its unique Order ID. This is useful in scenarios where you need to fetch order details for reporting, workflow branching, or integration with other systems (e.g., CRM, ERP).

Practical examples:

  • Retrieve an order's status and details after a customer places an order.
  • Use order data to trigger downstream processes, such as invoicing or fulfillment.
  • Integrate order retrieval into automated support workflows.

Properties

Name Type Meaning
Order ID String The unique identifier of the order you want to retrieve from Billwerk.

Output

The node outputs a JSON object containing the details of the requested order. The exact structure depends on the Billwerk API response, but typically includes fields such as:

  • id: The unique identifier of the order.
  • status: Current status of the order.
  • customerId: Associated customer.
  • items: List of items in the order.
  • createdAt, updatedAt: Timestamps for creation and last update.
  • Other order-specific metadata.

Note: The output will be a single JSON object (or an array if multiple inputs are processed), directly reflecting the Billwerk API's order representation.

Dependencies

  • External Service: Requires access to the Billwerk API.
  • Credentials: You must configure the billwerkApi credential in n8n with valid API keys or authentication details for your Billwerk account.

Troubleshooting

  • Invalid Order ID: If the provided Order ID does not exist, the node may return an error such as "Order not found" or similar. Double-check the Order ID value.
  • Authentication Errors: If credentials are missing or incorrect, errors like "Unauthorized" or "Invalid API key" may occur. Ensure your billwerkApi credentials are set up correctly in n8n.
  • API Rate Limits: Excessive requests may result in rate limit errors. Monitor your usage and consult Billwerk's API documentation for limits.
  • Continue On Fail: If enabled, failed executions will output an object with an error field containing the error message instead of stopping the workflow.

Links and References

Discussion