Actions4
- Product Actions
- Invoice Receipt Actions
Overview
This node integrates with the Moloni.pt API to create an Invoice Receipt. It allows users to generate detailed invoice receipts by specifying various invoice-related details such as dates, customer information, products, payments, delivery details, and discounts. This is useful for automating invoicing workflows in businesses that use Moloni.pt for their accounting and sales processes.
Typical scenarios include:
- Automatically creating invoice receipts after a sale or service completion.
- Integrating e-commerce platforms or CRMs with Moloni.pt to streamline billing.
- Managing complex invoices with multiple products, payment records, and delivery instructions.
Example: After a customer places an order, this node can be used to create an official invoice receipt including product details, payment methods, and delivery information, all recorded in Moloni.pt.
Properties
| Name | Meaning |
|---|---|
| Date | The date of the invoice receipt (required). |
| Expiration Date | The expiration date of the invoice receipt (required). |
| Maturity Date ID | Identifier for the maturity date setting. |
| Document Set ID | Identifier for the document set associated with the invoice (required). |
| Customer ID | Identifier of the customer for whom the invoice is created (required). |
| Alternate Address ID | Identifier for an alternate address if different from the customer's main address. |
| Our Reference | Internal reference note for the invoice. |
| Your Reference | External reference note for the invoice. |
| Financial Discount | Financial discount amount applied to the invoice. |
| EAC ID | Identifier related to accounting classification. |
| Salesman ID | Identifier of the salesman responsible for the invoice. |
| Salesman Commission | Commission amount for the salesman. |
| Special Discount | Any special discount applied to the invoice. |
| Related Documents Notes | Notes about related documents connected to this invoice. |
| Products | Collection of products included in the invoice. Each product requires a Product ID. |
| Payments | Collection of payment records. Each payment includes method ID, date, value, and optional notes. |
| Exchange Currency ID | Identifier for the currency used in exchange rates. |
| Exchange Rate | Exchange rate value applied to the invoice. |
| Delivery Method ID | Identifier for the delivery method chosen. |
| Delivery Datetime | Date and time scheduled for delivery. |
| Delivery Departure Address | Address where the delivery departs from. |
| Delivery Departure City | City of the delivery departure location. |
| Delivery Departure Zip Code | Zip code of the delivery departure location. |
| Delivery Departure Country | Country identifier of the delivery departure location. |
| Delivery Destination Address | Address where the delivery is destined. |
| Delivery Destination City | City of the delivery destination. |
| Delivery Destination Zip Code | Zip code of the delivery destination. |
| Delivery Destination Country | Country identifier of the delivery destination. |
| Vehicle ID | Identifier of the vehicle used for delivery. |
| Vehicle Name | Name of the vehicle used for delivery. |
| Vehicle Number Plate | Number plate of the vehicle used for delivery. |
| Notes | Additional notes related to the invoice receipt. |
| Status | Status code of the invoice receipt. |
| Generate MB Reference | Flag indicating whether to generate a Multibanco reference number. |
Output
The node outputs JSON data representing the created invoice receipt as returned by the Moloni.pt API. This typically includes identifiers, status, timestamps, and any other metadata related to the newly created invoice receipt.
If binary data were involved (e.g., PDF invoice files), it would be summarized here, but this node focuses on JSON output only.
Dependencies
- Requires an active connection to the Moloni.pt API.
- Needs an API authentication token configured in n8n credentials (an OAuth2 or API key credential).
- Network access to
https://api.moloni.pt/v1/must be available.
Troubleshooting
- Missing Required Fields: Errors may occur if required fields like Date, Expiration Date, Document Set ID, or Customer ID are not provided. Ensure these are filled correctly.
- Invalid IDs: Using invalid or non-existent IDs for customers, products, or other referenced entities will cause API errors. Verify IDs before submission.
- Authentication Failures: If the API credentials are incorrect or expired, the node will fail to authenticate. Refresh or reconfigure credentials as needed.
- API Rate Limits: Excessive requests might trigger rate limiting by Moloni.pt. Implement retries or delays if necessary.
- Network Issues: Connectivity problems to the Moloni.pt API endpoint will cause failures. Check network settings and firewall rules.