Actions29
- Cliente Actions
- Antecipação Actions
- Assinatura Actions
- Cobrança Actions
- Link De Pagamento Actions
- Webhook Actions
Overview
This node integrates with the Asaas API to manage "Antecipação" (anticipation of receivables) operations. Specifically, the Get Many operation retrieves multiple anticipation records from the Asaas platform, allowing users to filter and limit the results based on criteria such as status and creation date.
Typical use cases include:
- Fetching a list of anticipations for financial reconciliation or reporting.
- Filtering anticipations by their approval status to monitor pending or rejected requests.
- Retrieving anticipations created within a specific date range for auditing purposes.
For example, a user might want to retrieve all approved anticipations created in the last month, limited to 50 results, to review which receivables have been successfully anticipated.
Properties
| Name | Meaning |
|---|---|
| Limite | Maximum number of anticipation records to return. Minimum value is 1. Default is 50. |
| Status (Filtro) | Filter anticipations by status. Options: - Aprovada (APPROVED) - Cancelada (CANCELLED) - Pendente (PENDING) - Processada (PROCESSED) - Rejeitada (REJECTED) - Todos (all statuses) |
| Data Inicial | Filter anticipations created on or after this date/time. |
| Data Final | Filter anticipations created on or before this date/time. |
Output
The output is an array of JSON objects representing anticipation records retrieved from the Asaas API. Each item corresponds to one anticipation entity with its full details as returned by the API.
The structure of each JSON object depends on the Asaas API response for anticipations but typically includes fields such as:
- Anticipation ID
- Status
- Creation date
- Total value
- Payments involved
- Observations or notes
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Asaas API.
- The node uses the Asaas API base URL, switching between sandbox and production environments based on credential configuration.
- No additional external dependencies are required beyond the Asaas API access.
Troubleshooting
- Package Removed Error: If the node throws an error indicating the package was removed from npm, it means the underlying integration package is no longer available. The recommended action is to remove this node from your workflow and update to a supported version or alternative.
- Invalid API Key or Authentication Errors: Ensure that the API key credential is correctly configured and has the necessary permissions.
- Empty Results: If no anticipations are returned, verify the filter parameters (status, dates) and ensure there are matching records in the Asaas account.
- Limit Parameter Issues: Setting the limit below 1 will cause errors; always use a minimum of 1.
- Date Format: Date filters must be valid ISO 8601 date-time strings; invalid formats may cause request failures.