Overview
This n8n node integrates with the Asaas API to manage customer data. Specifically, for the Cliente (Customer) resource and the Obter (Get) operation, the node retrieves detailed information about a specific customer from your Asaas account using their unique customer ID.
Common scenarios:
- Fetching customer details to enrich workflow data.
- Verifying customer existence or status before processing payments or subscriptions.
- Synchronizing customer records between Asaas and other systems.
Practical example:
You might use this node in a workflow where, after receiving a payment notification, you want to fetch and log all details of the paying customer.
Properties
| Name | Type | Meaning |
|---|---|---|
| ID do Cliente | String | The unique identifier of the customer in Asaas whose details you want to retrieve. |
Output
The output is a JSON object containing all available details of the requested customer as returned by the Asaas API. Typical fields may include:
{
"id": "cus_1234567890",
"name": "João da Silva",
"cpfCnpj": "12345678901",
"email": "joao@email.com",
"phone": "1133224455",
"mobilePhone": "11999998888",
"address": "Rua Exemplo",
"addressNumber": "100",
"complement": "Apto 10",
"province": "SP",
"postalCode": "01234567",
...
}
Note: The actual structure depends on the Asaas API response.
Dependencies
- External Service: Requires access to the Asaas API.
- Credentials: You must configure an
asaasApicredential in n8n with your Asaas API key.
Troubleshooting
Common issues:
- Invalid Customer ID: If the provided "ID do Cliente" does not exist, the node will return an error message from the Asaas API.
- Authentication Errors: If the API key is missing or invalid, you'll receive authentication errors.
- Network Issues: Connectivity problems can cause request failures.
Error messages and resolutions:
"Customer not found": Check that the "ID do Cliente" is correct and exists in your Asaas account."Invalid API Key": Ensure your Asaas credentials are correctly set up in n8n."Unknown error": This generic message appears if the error type is not recognized; check logs for more details.