Asaas icon

Asaas

Integração com a API do Asaas para pagamentos e cobranças
Join our community

Actions29

Overview

This node integrates with the Asaas API to manage customer data within payment and billing workflows. Specifically, the "Cliente" (Customer) resource with the "Obter" (Get) operation retrieves detailed information about a single customer by their unique ID.

Common scenarios where this node is beneficial include:

  • Fetching customer details for invoicing or payment processing.
  • Synchronizing customer data between Asaas and other systems.
  • Validating customer existence before creating payments or subscriptions.

Practical example:

  • You have a workflow that triggers when a new order is placed. Using this node, you can retrieve the customer's full profile from Asaas by their ID to attach relevant billing information or send personalized notifications.

Properties

Name Meaning
ID Do Cliente The unique identifier of the customer in Asaas (e.g., cus_000005219613). This is required.

Output

The output contains a JSON object representing the customer data retrieved from the Asaas API. This includes all available fields for the customer such as name, email, phone numbers, address details, and identification numbers.

Example structure (simplified):

{
  "id": "cus_000005219613",
  "name": "Customer Name",
  "email": "customer@example.com",
  "cpfCnpj": "12345678900",
  "mobilePhone": "+5511999999999",
  "phone": "+551133333333",
  "postalCode": "12345678",
  "addressNumber": "100",
  "addressComplement": "Apartment 101"
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Asaas API.
  • The node uses the Asaas API base URL, which switches between sandbox and production environments based on the credential configuration.
  • No additional external services are required beyond the Asaas API.

Troubleshooting

  • Package Removed Error: If the node throws an error indicating the package was removed from npm, it means the underlying integration package is no longer available. The recommended action is to remove this node from your workflow and seek an updated integration.
  • Invalid Customer ID: Providing an incorrect or non-existent customer ID will result in an API error. Verify the ID format and existence in your Asaas account.
  • Authentication Errors: Ensure the API key credential is correctly configured and has the necessary permissions.
  • Network Issues: Timeouts or connectivity problems may cause request failures. Check network access to the Asaas API endpoints.

Links and References

Discussion