Actions22
Overview
The node integrates with the Distru API to manage various business entities and operations related to inventory, orders, invoices, payments, and more. Specifically, the "Post Invoice Payment" operation allows users to create a payment record for an existing invoice in Distru.
This operation is useful in scenarios where you want to automate recording payments against invoices, such as when integrating payment processing systems or updating accounting records automatically after receiving payments.
Practical example:
After a customer pays an invoice via an external payment gateway, this node can be used to post that payment to the corresponding invoice in Distru, ensuring your financial records stay synchronized without manual entry.
Properties
| Name | Meaning |
|---|---|
| Invoice ID | The unique identifier of the invoice to which the payment will be applied. |
| Payment Method ID | The identifier of the payment method used for this payment. |
| Amount | The amount of the payment. This value will be rounded to 2 decimal places. |
| Payment Datetime | The date and time when the payment was made, in ISO 8601 format (e.g., 2020-01-01T00:00:00.000000Z). |
| Description | A description or note about the payment. |
| QuickBooks Deposit Account ID | The ID of the QuickBooks deposit account where the payment should be recorded. Cannot be used together with QuickBooks Deposit Account Name. |
| QuickBooks Deposit Account Name | The name of the QuickBooks deposit account where the payment should be recorded. Cannot be used together with QuickBooks Deposit Account ID. |
Output
The output is a JSON object representing the payment record created in Distru. It contains details returned by the Distru API about the posted payment, including confirmation of the amount, payment method, datetime, description, and any linked accounts.
The node does not output binary data.
Dependencies
- Requires an API token credential for authenticating with the Distru API.
- The node uses the Distru public API endpoint, either production (
https://app.distru.com/public/v1) or staging (https://staging.distru.com/public/v1), depending on configuration. - No additional external dependencies are required beyond the API token.
Troubleshooting
- Missing API Token: If the API token is not set or invalid, the node will throw an error stating that the Distru API token is not set. Ensure the API token credential is configured correctly.
- Invalid Invoice or Payment Method ID: Providing incorrect or non-existent IDs may cause the API to return errors. Verify that the invoice and payment method IDs exist in Distru.
- Conflicting QuickBooks Deposit Account Fields: Both QuickBooks deposit account ID and name cannot be provided simultaneously. Use only one to avoid errors.
- Date Format Errors: The payment datetime must be in valid ISO 8601 format. Incorrect formatting may cause the request to fail.
- API Errors: Any other errors from the Distru API will be propagated. Check the error message for details and verify the input parameters.
Links and References
- Distru API Documentation (general reference for API endpoints and data models)
- ISO 8601 Date Format: https://en.wikipedia.org/wiki/ISO_8601