Superlogica icon

Superlogica

Consumir API do Superlogica Condomínios
Join our community

Actions42

Overview

This node integrates with the Superlogica Condomínios API, specifically allowing users to list bank transactions ("Movimentação Bancária"). It is useful for retrieving financial transaction data related to bank accounts within a condominium management context. Typical scenarios include generating financial reports, auditing bank movements, or syncing transaction data with other systems.

For example, a property manager could use this node to fetch all bank transactions for a specific bank account and condominium over a given date range to reconcile accounts or monitor cash flow.

Properties

Name Meaning
ID da Conta Bancária The unique identifier of the bank account from which to list transactions (required).
ID do Condomínio The unique identifier of the condominium associated with the bank account (required).
Data Inicial Optional start date to filter transactions, in MM/DD/YYYY format.
Data Final Optional end date to filter transactions, in MM/DD/YYYY format.

Output

The node outputs an array of JSON objects, each representing a bank transaction retrieved from the Superlogica API. Each item corresponds to one transaction and includes all relevant details as provided by the API response.

If the API supports binary data for transactions (e.g., attached documents), it would be included in the binary output field; however, based on the static code and properties, this node primarily outputs JSON data describing the transactions.

Dependencies

  • Requires an API key credential for authenticating with the Superlogica Condomínios API.
  • The node uses the base URL https://api.superlogica.net/v2/condor by default unless overridden in credentials.
  • Proper configuration of the API authentication tokens (app token and access token) is necessary.

Troubleshooting

  • Missing Credentials Error: If credentials are not provided or invalid, the node throws an error indicating that credentials were not supplied. Ensure that the API key and tokens are correctly configured in n8n.
  • Date Format Issues: The optional date filters must be in MM/DD/YYYY format. Incorrect formats may cause the API to reject the request or return no results.
  • API Rate Limits or Connectivity: Network issues or API rate limits might cause errors or incomplete data. Check network connectivity and API usage quotas.
  • Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output JSON for failed items.

Links and References

Discussion