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 recurring subscriptions, among other payment-related resources. Specifically, the "Assinatura" (Subscription) resource with the "Obter" (Get) operation allows users to retrieve detailed information about a specific subscription by its unique ID.
Common scenarios where this node is beneficial include:
- Fetching subscription details for customer management or billing reconciliation.
- Automating workflows that require validation or processing based on subscription status or attributes.
- Integrating subscription data into CRM, ERP, or reporting systems.
Practical example:
- A business uses this node to automatically fetch subscription details when a customer support ticket is created, enabling agents to view current subscription status and billing info without manual lookup.
Properties
| Name | Meaning |
|---|---|
| ID Da Assinatura * | Unique identifier of the subscription to retrieve |
The property "ID Da Assinatura *" is required and expects a string representing the unique subscription ID in the Asaas system.
Output
The node outputs JSON data representing the subscription object retrieved from the Asaas API. This includes all subscription details such as customer ID, billing type, value, next due date, cycle, description, external reference, end date, maximum payments, and potentially split payment configuration.
The output structure corresponds directly to the Asaas API's subscription resource representation.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Asaas API.
- The node supports both sandbox and production environments, selectable via credentials.
- Relies on the Asaas REST API v3 endpoints.
- Uses internal helper functions to perform HTTP requests and handle pagination if applicable.
Troubleshooting
- Package Unavailability: If the node throws an error indicating the package was removed from npm, it means the integration package is no longer available and should be removed from your n8n installation.
- Invalid Subscription ID: Providing an invalid or empty subscription ID will cause the API request to fail. Ensure the ID is correct and non-empty.
- Authentication Errors: Missing or incorrect API key credentials will result in authentication failures. Verify that the API key is valid and has appropriate permissions.
- Network Issues: Timeouts or connectivity problems can cause request failures. Check network access to the Asaas API endpoints.
- API Rate Limits: Excessive requests may trigger rate limiting; implement retry logic or reduce request frequency if needed.