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 payment links, among other resources. Specifically, the "Get Many" operation for the "Link De Pagamento" (Payment Link) resource retrieves multiple payment links from the Asaas platform. This is useful when you want to list or filter payment links in bulk, for example, to display active payment links on a dashboard or to process them further in an automation workflow.
Practical examples include:
- Fetching all active payment links to send reminders or notifications.
- Retrieving a limited number of payment links for reporting purposes.
- Filtering payment links by their status (active/inactive/all) to analyze usage patterns.
Properties
| Name | Meaning |
|---|---|
| Limite | Maximum number of payment links to return. Minimum value is 1. Default is 50. |
| Status (Filtro) | Filter payment links by status. Options: "Ativo" (active), "Inativo" (inactive), "Todos" (all). |
Output
The output is an array of JSON objects, each representing a payment link retrieved from the Asaas API. Each object contains the full details of a payment link as returned by the API, including fields such as name, description, billing type, charge type, value, due date, subscription cycle, and status (active or not).
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Asaas API.
- The node uses the Asaas API base URL, which switches between sandbox and production environments based on the credential configuration.
- No additional external services are required beyond the Asaas API.
Troubleshooting
- Package Availability: The node checks if its npm package is still available. If it has been removed, it throws an error advising to remove the node from the installation.
- API Authentication Errors: If the API key is invalid or missing, requests will fail. Ensure the API key credential is correctly configured.
- Invalid Parameters: Providing invalid values for filters or limits may cause errors. For example, limit must be at least 1.
- Network Issues: Timeouts or connectivity problems with the Asaas API can cause request failures.
- Empty Results: If no payment links match the filter criteria, the output will be an empty array.
Links and References
- Asaas API Documentation (official API docs)
- n8n Documentation (for general node usage and credential setup)