AsaasInstall

Overview

This node integrates with the Asaas API to manage webhooks and other payment-related resources. Specifically, for the Webhook - Obter (Get) operation, it retrieves detailed information about a specific webhook by its unique ID. This is useful when you want to fetch the configuration or status of an existing webhook registered in your Asaas account.

Common scenarios include:

• Verifying webhook details before updating or deleting.
• Auditing webhook configurations programmatically.
• Integrating webhook data retrieval into automated workflows for monitoring or reporting.

Example: You have a webhook set up to receive payment notifications and want to confirm its URL and event subscriptions via n8n before making changes.

Properties

The property "ID Do Webhook *" is required and expects the unique webhook ID as a string.

Output

The node outputs the webhook data as JSON in the json field of the output item. The structure corresponds directly to the webhook object returned by the Asaas API, typically including fields such as:

• id: The webhook's unique identifier.
• name: The name given to the webhook.
• url: The callback URL where events are sent.
• email: Email associated with the webhook notifications.
• events: Array of event types the webhook listens to.
• sendType: How notifications are sent (e.g., sequentially).
• apiVersion: Version of the API used.
• enabled: Whether the webhook is active.
• interrupted: Whether the webhook is interrupted.
• authToken: Optional authentication token for securing webhook calls.

No binary data output is involved in this operation.

Dependencies

• Requires an API key credential for authenticating with the Asaas API.
• The node uses the Asaas REST API endpoint, switching between sandbox and production based on credential environment settings.
• No additional external services beyond Asaas are needed.

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 alternative solution.
• Invalid Webhook ID: Providing an incorrect or non-existent webhook ID will result in an API error. Ensure the ID is correct and exists in your Asaas account.
• Authentication Errors: Missing or invalid API keys will cause authentication failures. Verify that the API key credential is correctly configured.
• Network Issues: Timeouts or connectivity problems can prevent successful API calls. Check network access and Asaas service status.

Links and References

• Asaas API Documentation - Webhooks
• n8n Documentation - Creating Custom Nodes
• Asaas Official Website