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 payments and charges ("Cobrança"). Specifically, the "Obter" (Get) operation under the "Cobrança" resource retrieves detailed information about a specific payment or charge by its unique ID.

Common scenarios where this node is beneficial include:

  • Fetching the status and details of a particular payment for reconciliation or reporting.
  • Verifying payment information before triggering downstream workflows.
  • Auditing or monitoring individual transactions in automated financial processes.

Practical example:

  • A business uses this node to retrieve payment details after a customer completes a transaction on their website, enabling them to update order statuses or send confirmation emails automatically.

Properties

Name Meaning
ID Da Cobrança * The unique identifier of the payment/charge to retrieve. This is a required string input.

Output

The node outputs a JSON object representing the payment details as returned by the Asaas API. This includes all relevant fields of the payment such as customer info, billing type, value, due date, description, status, and any other metadata provided by the API.

If multiple items were returned (not applicable here since this is a single get operation), they would be output as an array of JSON objects.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Asaas API.
  • The node supports both sandbox and production environments, selectable via credentials configuration.
  • No additional external dependencies beyond the Asaas API.

Troubleshooting

  • Package Removed Error: If the node throws an error indicating the package was removed from npm and is no longer available, it means the underlying integration package is deprecated or missing. The user should remove the node from their workflow or update to a supported version.
  • Invalid Payment ID: Providing an empty or invalid payment ID will cause the API request to fail. Ensure the "ID Da Cobrança" property contains a valid payment ID string.
  • API Authentication Errors: If the API key is incorrect or missing, requests will fail with authentication errors. Verify that the API key credential is correctly configured.
  • Network Issues: Timeouts or connectivity problems can cause request failures. Check network access to the Asaas API endpoints.
  • Continue On Fail: If enabled, the node will output error messages in the JSON output instead of stopping execution, allowing workflows to handle errors gracefully.

Links and References

Discussion