Billwerk TriggerInstall

Overview

The Billwerk Trigger node for n8n allows you to receive real-time updates from the Billwerk subscription management platform via webhooks. It listens for selected events (such as contract changes, invoice creation, payment status updates, etc.) and triggers your n8n workflow when these events occur in your Billwerk account.

Common scenarios:

• Automate customer onboarding or offboarding based on contract or customer events.
• Sync billing or payment data with other systems (e.g., CRM, accounting).
• Notify teams or trigger alerts when invoices are created, payments fail, or contracts are cancelled.

Practical examples:

• When a new invoice is created in Billwerk, automatically send an email to the customer.
• If a payment fails, create a support ticket in your helpdesk system.
• On successful contract creation, update a record in your database.

Properties

Event options include (not exhaustive):

• Accounting Export File Created: On successful accounting export file creation
• Contract Cancelled: When a notice of cancellation has been handed in
• Invoice Created: When an invoice or credit note PDF was created and sent
• Payment Failed: On payment errors
• Customer Created: On successful customer creation
• ...and many more (see full property definition above).

Output

The node outputs the raw webhook payload received from Billwerk in the json field. The structure of this output depends on the event type but generally includes all fields sent by Billwerk for the triggered event.

Example output:

[
  {
    "json": {
      // All properties from the Billwerk webhook body, e.g.:
      "Event": "InvoiceCreated",
      "Data": {
        "InvoiceId": "12345",
        "CustomerId": "67890",
        // ...other relevant fields
      },
      // ...any additional metadata provided by Billwerk
    }
  }
]

• No binary data is produced by this node.

Dependencies

• External Service: Requires a Billwerk account with API access.
• API Key/Credentials: Needs valid Billwerk API credentials configured in n8n under the name billwerkApi.
• n8n Configuration: The node must be accessible from the internet so Billwerk can reach its webhook endpoint.

Troubleshooting

Common issues:

• Webhook not triggering: Ensure your n8n instance is publicly accessible and the webhook URL is correctly registered in Billwerk.
• Authentication errors: Double-check your Billwerk API credentials in n8n.
• Missing events: Make sure you have selected the correct events in the node configuration.

Error messages:

• "401 Unauthorized" or similar: Indicates invalid or missing API credentials.
• "Webhook not found" or "404 Not Found": The webhook may have been deleted or the URL changed; try re-creating the webhook.
• No data received: Check if Billwerk is sending the expected events and that your n8n instance is reachable.

Links and References

• Billwerk Documentation
• n8n Webhook Documentation
• n8n Credentials Setup