Actions13
- Category Actions
- Payment Bank Actions
- Bill Actions
- Payment Status Actions
- Webhook Actions
Overview
This node integrates with the Bizappay API to manage billing operations. Specifically, the "Bill" resource's "Bulk Create" operation allows users to create multiple bills simultaneously by submitting an array of bill objects in JSON format. This is useful for businesses or applications that need to generate many invoices or payment requests at once, such as batch invoicing customers, processing multiple orders, or automating recurring billing setups.
Practical examples include:
- A company generating monthly utility bills for all customers in one request.
- An e-commerce platform creating bills for multiple orders placed during a sales event.
- Subscription services issuing renewal invoices in bulk.
The node supports batching to control how many bills are processed concurrently, improving performance and avoiding API rate limits.
Properties
| Name | Meaning |
|---|---|
| Bills Data | Array of bill objects to create in bulk (JSON format). Each object should contain details like name, amount, category code, payer information, and description. |
| Batch Size | Number of bills to process simultaneously. Accepts values from 1 to 10. Controls concurrency of the bulk creation process. |
Output
The output is a JSON array where each element corresponds to the result of processing a bill or a batch of bills. The structure includes:
- For each successfully created bill, the response contains details returned by the Bizappay API, including identifiers like
billIdand URLs such asbillUrl. - Additional metadata may be included, such as quick actions (e.g., payment URL, next steps) to facilitate post-creation workflows.
- In case of errors, the output will contain error messages describing what went wrong.
No binary data is produced by this operation.
Dependencies
- Requires an active connection to the Bizappay API using a valid API key credential configured in n8n.
- The node uses internal helper functions to make authenticated HTTP POST requests to Bizappay endpoints.
- No additional external dependencies beyond the Bizappay API and standard n8n environment.
Troubleshooting
- Invalid JSON in Bills Data: Ensure the JSON array of bills is correctly formatted. Malformed JSON will cause parsing errors.
- API Rate Limits: Setting a very high batch size might lead to API throttling. Keep batch size between 1 and 10 as recommended.
- Missing Required Fields: Each bill object must include required fields such as
name,amount,category,payer_name,payer_email, andpayer_phone. Missing these will cause API errors. - Invalid Email or Phone Format: Payer email must be a valid email format; phone numbers must follow Malaysian phone number formats. Invalid formats will trigger validation errors.
- API Errors: If the Bizappay API returns errors (e.g., authentication failure, invalid category), the node will throw descriptive errors. Check credentials and input data accordingly.
Links and References
- Bizappay API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- JSON Syntax Guide
If you need further details on other operations or resources, feel free to ask!