Superlogica icon

Superlogica

Consumir API do Superlogica Condomínios
Join our community

Actions42

Overview

This node integrates with the Superlogica Condomínios API to list boletos (payment slips) associated with a condominium. It allows users to retrieve boleto records filtered by status and date range, which is useful for financial management and tracking payments within condominium administration.

Common scenarios include:

  • Fetching all boletos issued for a specific condominium.
  • Filtering boletos by their payment status (e.g., open, paid, canceled).
  • Retrieving boletos within a specific date range to generate reports or reconcile accounts.

Practical example: A property manager wants to generate a report of all unpaid boletos issued in the last month to follow up on pending payments.

Properties

Name Meaning
ID do Condomínio The unique identifier of the condominium for which boletos are being listed.
Filtrar por Status Filter boletos by their status. Options: Todos (all), Em Aberto (open), Pagos (paid), Cancelados (canceled).
Data Inicial Start date to filter boletos (format: MM/DD/YYYY).
Data Final End date to filter boletos (format: MM/DD/YYYY).

Output

The node outputs an array of JSON objects, each representing a boleto record retrieved from the Superlogica API. Each item contains detailed information about a boleto, such as its status, due date, amount, and related condominium data.

If the operation encounters errors and "Continue On Fail" is enabled, the output will include error messages corresponding to the failed items.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Superlogica API.
  • The API base URL defaults to https://api.superlogica.net/v2/condor but can be configured via credentials.
  • Proper configuration of the API token and access token is necessary for successful requests.

Troubleshooting

  • Missing Credentials: If the API credentials are not provided or invalid, the node will throw an error indicating that credentials are missing.
  • Invalid Date Format: Providing dates in a format other than MM/DD/YYYY may cause the API to reject the request or return no results.
  • API Errors: Network issues or incorrect tokens can lead to API errors; enabling "Continue On Fail" helps handle these gracefully.
  • Empty Results: If filters are too restrictive (e.g., date range or status), the node might return an empty list.

To resolve common errors:

  • Ensure API credentials are correctly set up in n8n.
  • Verify date inputs follow the required format.
  • Check network connectivity and API service status.

Links and References

Discussion