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, for the Bill - Delete operation, it allows users to delete an existing bill by specifying its unique Bill ID. This is useful in scenarios where a bill was created erroneously, is no longer needed, or must be removed due to cancellation or error.
Practical examples include:
- Automatically deleting bills that are outdated or invalid as part of a cleanup workflow.
- Removing bills when a customer cancels an order before payment.
- Managing billing lifecycle by programmatically deleting bills after refunds or disputes.
Properties
| Name | Meaning |
|---|---|
| Bill ID | The unique identifier of the bill to delete. This is required to specify which bill to remove. |
Output
The output JSON object contains the response from the Bizappay API after attempting to delete the specified bill. Typically, this will include a status indicating success or failure of the deletion request.
Example structure of the output JSON:
{
"status": "ok",
"message": "Bill deleted successfully"
}
If the deletion fails (e.g., bill not found), the output will contain an error message describing the issue.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Bizappay API using a valid API authentication token credential configured in n8n.
- The node uses HTTP POST requests to Bizappay endpoints.
- No additional external dependencies beyond the Bizappay API and standard n8n environment.
Troubleshooting
- Missing Bill ID: If the Bill ID property is empty or invalid, the node will throw an error stating that the Bill ID is required. Ensure you provide a valid Bill ID.
- Bill Not Found: If the specified Bill ID does not exist, the API may return an error. Verify the Bill ID is correct and exists in your Bizappay account.
- API Authentication Errors: If the API key or token is invalid or expired, the node will fail to authenticate. Check your API credentials and refresh tokens if necessary.
- Network Issues: Connectivity problems can cause request failures. Confirm network access to Bizappay API endpoints.
- Unexpected Response Format: If the API returns non-serializable data or unexpected formats, the node may report serialization errors.
Links and References
- Bizappay API Documentation (for detailed API endpoint info)
- n8n Documentation on Creating Custom Nodes
- n8n Expressions Guide (useful for dynamic Bill ID input)
This summary focuses exclusively on the "Bill" resource with the "Delete" operation as requested.