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 (assinaturas). Specifically, the "Criar" operation under the "Assinatura" resource allows users to create new subscription records for customers. This is useful for automating billing cycles, managing customer subscriptions, and handling payment schedules in Brazilian real currency.
Common scenarios include:
- Creating monthly or annual subscription plans for services or products.
- Automating recurring payments via boleto bancário, credit card, PIX, or letting the customer choose the payment method.
- Managing subscription lifecycle details such as next due date, maximum number of payments, and optional end dates.
Practical example:
A SaaS company wants to bill customers monthly via credit card automatically. Using this node, they can create a subscription specifying the customer ID, billing type as credit card, monthly cycle, and the amount to be charged each month.
Properties
| Name | Meaning |
|---|---|
| Cliente * | Select or enter the customer ID (must start with "cus_"). Can be selected from a list or entered by ID. |
| Tipo De Cobrança * | Payment method for the subscription. Options: Boleto Bancário, Cartão De Crédito, PIX, Indefinido (Cliente Escolhe). |
| Valor * | Subscription amount in Brazilian reais (minimum 0.01). |
| Próximo Vencimento * | Date and time of the next payment due date for the subscription. |
| 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 external system reference identification. |
| Data De Término | Optional subscription end date. |
| Máximo De Cobranças | Maximum number of payments allowed (0 means unlimited). |
(* indicates required fields)
Output
The node outputs JSON data representing the created subscription object returned by the Asaas API. This includes all subscription details such as customer ID, billing type, value, next due date, cycle, description, external reference, end date, max payments, and any split commission configuration applied.
No binary data output is produced by this operation.
Dependencies
- Requires an active Asaas API key credential configured in n8n.
- The node uses the Asaas API endpoint, switching between sandbox and production based on credential environment.
- No additional external dependencies beyond the Asaas API.
Troubleshooting
- Invalid Customer ID: If the customer ID is missing or does not start with "cus_", the node throws an error indicating the customer field is mandatory and must contain a valid ID.
- API Access Issues: If the Asaas API package is removed or unavailable, the node will throw an error instructing to remove the node from the installation.
- Incorrect Property Values: Ensure required fields are filled and values like "Valor" meet minimum constraints (>= 0.01).
- Network or Authentication Errors: Verify that the API key credential is correct and has necessary permissions.