Overview
This node interacts with the Asaas API to manage customer data. Specifically, the "Restaurar" (Restore) operation for the "Cliente" (Customer) resource allows users to restore a previously deleted or deactivated customer in the Asaas system.
Common scenarios where this node is beneficial include:
- Reactivating customers who were accidentally deleted.
- Restoring customer records that need to be re-enabled for billing or communication.
- Managing customer lifecycle states programmatically within an automation workflow.
For example, if a customer was removed but later needs to be reinstated without recreating their profile, this node can send a restore request to Asaas to recover that customer's data.
Properties
| Name | Meaning |
|---|---|
| ID Do Cliente | Unique identifier of the customer to restore |
Output
The output is a JSON object representing the restored customer as returned by the Asaas API. It typically includes all customer details such as name, identification numbers, email, status, and other metadata fields.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Asaas API.
- The node uses either the production or sandbox Asaas API endpoint depending on the configured environment in the credentials.
- Proper network access to
https://api.asaas.com/v3orhttps://api-sandbox.asaas.com/v3is necessary.
Troubleshooting
- Invalid Customer ID: If the provided customer ID does not exist or is incorrect, the API will return an error. Verify the ID before running the node.
- Authentication Errors: Missing or invalid API keys will cause authentication failures. Ensure the API key credential is correctly set up.
- Permission Issues: The API user must have permissions to restore customers.
- API Rate Limits: Excessive requests may lead to rate limiting; handle errors accordingly.
- Network Issues: Connectivity problems to the Asaas API endpoints will cause request failures.
If the node throws an error message related to HTTP status codes or API responses, check the message details for guidance on resolving issues such as invalid parameters or authorization failures.