Billplz icon

Billplz

Billplz using API for payment gateway

Overview

This node integrates with the Billplz payment gateway API to manage collections and bills. Specifically, for the "Get a Collection" operation under the "Collection" resource, it retrieves detailed information about a specific collection by its ID. This is useful when you want to query existing collections to check their status or details without creating new ones.

Practical scenarios include:

  • Fetching collection details to display in dashboards or reports.
  • Verifying collection data before creating related bills.
  • Automating workflows that depend on collection metadata from Billplz.

Properties

Name Meaning
Collection ID The unique identifier of the collection to retrieve. A string representing the collection ID (e.g., "346543278").

Output

The node outputs a JSON object containing the details of the requested collection as returned by the Billplz API. This typically includes fields such as collection ID, title, creation date, and any other metadata associated with the collection.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Billplz API.
  • Makes HTTP requests to https://www.billplz.com/api/v3/collections/{collection_id} using Basic Authentication.
  • The node expects valid credentials configured in n8n to authorize API calls.

Troubleshooting

  • Invalid Collection ID: If the provided collection ID does not exist or is malformed, the API will likely return an error. Verify the collection ID is correct.
  • Authentication Errors: Ensure the API key credentials are correctly set up and have sufficient permissions.
  • Network Issues: Connectivity problems may cause request failures; verify network access to Billplz API endpoints.
  • API Rate Limits: Excessive requests might be throttled by Billplz; consider adding delays or retries if needed.

Common error messages usually come directly from the Billplz API and should be interpreted according to their documentation.

Links and References

Discussion