Easybill icon

Easybill

Interact with Easybill API

Actions13

Overview

This node integrates with the Easybill API to manage various resources related to billing and invoicing. Specifically, for the Document-Payments resource with the Delete operation, it allows users to delete a payment record associated with a document in Easybill. This is useful in scenarios where a payment was recorded incorrectly or needs to be removed due to cancellation or error.

Practical examples include:

  • Removing a mistakenly entered payment from an invoice.
  • Deleting payments that were refunded or reversed.
  • Cleaning up test data during development or troubleshooting.

Properties

Name Meaning
Payment Select the payment to delete. You can either choose from a searchable list of payments or specify the payment ID directly (must be numeric).

Output

The node outputs a JSON array containing the result(s) of the delete operation. Typically, this will include confirmation details about the deleted payment or an empty object if no content is returned by the API. The output does not include binary data.

Example output structure might look like:

[
  {
    "success": true,
    "paymentId": "12345",
    "message": "Payment deleted successfully"
  }
]

(Note: Actual output depends on the Easybill API response.)

Dependencies

  • Requires an active connection to the Easybill API via an API key credential configured in n8n.
  • The node uses internal helper methods to fetch lists of payments for selection.
  • No additional external dependencies beyond the Easybill API and its authentication are required.

Troubleshooting

  • Invalid Payment ID: If you enter a non-numeric payment ID, the node will reject it due to validation rules. Ensure the payment ID consists only of digits.
  • Payment Not Found: Attempting to delete a payment that does not exist or has already been deleted may result in an error from the API. Verify the payment exists before deletion.
  • Authentication Errors: If the API key or credentials are invalid or expired, the node will fail to connect. Check your Easybill API credentials in n8n.
  • Network Issues: Connectivity problems can cause timeouts or failures. Ensure stable internet access.
  • API Rate Limits: Excessive requests may trigger rate limiting by Easybill. Implement retries or delays as needed.

Links and References

Discussion