Overview
This n8n node integrates with the Asaas API to manage customer records. Specifically, for the Cliente (Customer) resource and the Excluir (Delete) operation, the node allows you to delete a customer from your Asaas account by specifying their unique customer ID.
Common scenarios:
- Automating the removal of customers who have requested account deletion.
- Cleaning up test or duplicate customer records in bulk.
- Integrating with other systems to synchronize customer deletions.
Practical example:
You could use this node in a workflow that listens for account deletion requests from your application and automatically removes the corresponding customer from Asaas.
Properties
| Name | Type | Meaning |
|---|---|---|
| ID do Cliente | String | The unique identifier of the customer to be deleted in Asaas. This is required. |
Output
The output will be a JSON object reflecting the response from the Asaas API after attempting to delete the specified customer. Typically, this may include confirmation of deletion or an error message if the operation failed.
Example output:
{
"deleted": true,
"id": "cus_1234567890abcdef"
}
If an error occurs and "Continue On Fail" is enabled, the output will contain an error field:
{
"error": "Customer not found"
}
Dependencies
- External Service: Requires access to the Asaas API.
- API Key: You must configure valid Asaas API credentials in n8n under the credential type
asaasApi. - n8n Configuration: No additional environment variables are needed beyond the API key setup.
Troubleshooting
Common issues:
- Invalid or missing Customer ID: If the provided "ID do Cliente" does not exist, the API will return an error such as "Customer not found".
- Authentication errors: If the Asaas API credentials are incorrect or missing, the node will fail with an authentication error.
- Network issues: Connectivity problems between n8n and the Asaas API can cause timeouts or connection errors.
Error handling:
- If "Continue On Fail" is enabled, errors will be returned in the output JSON under the
errorfield, allowing workflows to proceed without interruption. - If not enabled, the workflow will stop on the first encountered error.