Actions30
Overview
This node integrates with the Perfex CRM system via the WON API, allowing users to interact programmatically with various CRM resources. Specifically, for the Fatura (Invoice) resource and the Listar (List/Get All) operation, the node fetches a list of invoices from the Perfex CRM.
Typical use cases include:
- Retrieving all invoices or a filtered subset based on criteria such as status, client ID, date ranges, etc.
- Paginating through large sets of invoices by specifying page number and limit.
- Automating invoice data retrieval for reporting, synchronization, or further processing in workflows.
For example, a user might configure this node to list all invoices issued in the last month with a limit of 100 results per page, enabling batch processing or integration with accounting systems.
Properties
| Name | Meaning |
|---|---|
| Opções Adicionais (options) | Collection of additional options to customize the listing: |
| - Limite (limit) | Maximum number of invoices to return (number). |
| - Página (page) | Page number of results to retrieve (number). |
| - Filtros (filters) | JSON string representing filters to apply to the search query (e.g., {"status":1}). |
These properties allow controlling pagination and filtering of the invoice list returned by the node.
Output
The output is an array of JSON objects, each representing an invoice record retrieved from the Perfex CRM. The structure corresponds directly to the API response for invoices and includes fields such as:
- Invoice ID
- Client ID
- Invoice number
- Date and due date
- Currency ID
- Subtotal and total amounts
- Status ID
- Project ID (if applicable)
- Items (line items in JSON format)
No binary data is output by this node.
Dependencies
- Requires a valid connection to the Perfex CRM WON API endpoint.
- Needs an API token credential configured in n8n to authenticate requests.
- Uses Axios HTTP client internally to perform REST API calls.
- The base URL and API token must be set in the node credentials.
Troubleshooting
- Invalid JSON in Filters: If the "Filtros" property contains malformed JSON, the node will throw an error. Ensure the filter string is valid JSON.
- Authentication Errors: If the API token is missing or invalid, the node returns an authentication error. Verify the API token in credentials.
- Resource Not Found: If no invoices match the filters or the resource path is incorrect, a "resource not found" error may occur.
- Connection Issues: Network problems or incorrect base URL configuration can cause connection errors.
- Limit and Page Values: Setting limits outside the allowed range (1 to 1000) or invalid page numbers may cause unexpected behavior.
Links and References
- Perfex CRM Official Website
- Perfex CRM WON API Documentation (Assumed, please verify actual API docs)
- Axios HTTP Client
This summary focuses exclusively on the "Fatura" resource with the "Listar" operation as requested, based on static analysis of the provided source code and input property definitions.