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 ("Assinatura"). The "Atualizar" (Update) operation allows users to modify an existing subscription's details such as customer, billing type, value, next due date, billing cycle, description, external reference, end date, and maximum number of payments.
Typical use cases include:
- Updating subscription payment methods or billing cycles when a customer changes their preferences.
- Adjusting subscription values or descriptions for promotions or corrections.
- Setting or modifying subscription end dates or limits on the number of charges.
For example, a business can update a customer's monthly subscription from boleto bancário (bank slip) to credit card billing, or extend the subscription end date.
Properties
| Name | Meaning |
|---|---|
| Cliente * | Select or enter the customer ID associated with the subscription. Must start with "cus_". |
| Tipo De Cobrança * | Billing type for the subscription. Options: Boleto Bancário, Cartão De Crédito, PIX, Indefinido (Cliente Escolhe). |
| Valor * | Subscription amount in Brazilian reais (BRL), minimum 0.01. |
| Próximo Vencimento * | Date and time of the next subscription due date. |
| Ciclo De Cobrança * | Billing frequency. Options: Anual, Bimestral, Mensal, Quinzenal, Semanal, Semestral, Trimestral. |
| Descrição | Optional description of the subscription. |
| Referência Externa | Optional free text field for identifying the subscription in your system. |
| Data De Término | Optional subscription end date. |
| Máximo De Cobranças | Maximum number of charges; 0 means unlimited. |
| ID Da Assinatura * | Unique identifier of the subscription to update. |
(* indicates required fields)
Output
The node outputs JSON data representing the updated subscription object returned by the Asaas API. This includes all subscription details after the update, such as customer info, billing type, value, next due date, cycle, description, external reference, end date, max payments, and any other metadata provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active Asaas API key credential configured in n8n.
- The node makes HTTP requests to the Asaas API endpoint (sandbox or production based on credential environment).
- No additional external dependencies beyond the Asaas API.
Troubleshooting
- Invalid Customer ID: If the customer ID does not start with "cus_" or is empty, the node throws an error indicating the customer field is mandatory and must be valid.
- API Request Failures: Network issues or invalid API keys will cause request errors. Verify API credentials and network connectivity.
- Package Availability: The node checks if its npm package is available; if removed, it throws an error advising removal of the node from the workflow.
- Invalid Property Values: Ensure numeric fields like "Valor" and "Máximo De Cobranças" meet minimum requirements; otherwise, the API may reject the request.