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 like customers, payments, subscriptions, webhooks, splits, and anticipations. Specifically, for the "Link De Pagamento" (Payment Link) resource with the "Obter" (Get) operation, it retrieves detailed information about a specific payment link by its unique ID.
Common scenarios where this node is beneficial include:
- Fetching details of a payment link to verify its status or properties.
- Automating workflows that depend on payment link data, such as sending reminders or updating records.
- Integrating payment link data into CRM or accounting systems.
Practical example:
- You have created a payment link for a customer and want to retrieve its current status and details programmatically within an automation workflow.
Properties
| Name | Meaning |
|---|---|
| ID Do Link * | The unique identifier of the payment link to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the payment link object retrieved from the Asaas API. This includes all relevant fields of the payment link such as name, description, billing type, charge type, value, due date, subscription cycle, end date, installment count, notification settings, active status, and potentially split payment configuration.
If multiple items were returned (not applicable for the "get" operation but for "getAll"), each item would be output as a separate JSON object in the array.
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 Removal Error: If the node throws an error stating the package was removed from npm and is no longer available, it indicates the node's underlying package is deprecated or unpublished. The recommended action is to remove this node from your installation.
- Invalid Payment Link ID: Providing an invalid or empty payment link ID will cause the API request to fail. Ensure the ID is correct and non-empty.
- API Authentication Errors: If the API key is missing, invalid, or lacks permissions, requests will fail. Verify the API key credential is correctly configured.
- Network Issues: Timeouts or connectivity problems can cause failures. Check network access to the Asaas API endpoints.
- Continue On Fail: If enabled, errors for individual items will be captured in the output JSON under an
errorfield instead of stopping execution.
Links and References
- Asaas API Documentation (official API docs)
- n8n Documentation (for general usage of n8n nodes and credentials)