Conta Azul API icon

Conta Azul API

Allows making requests to the Conta Azul API

Overview

This node integrates with the Conta Azul API to search for expenses filtered by various criteria. It allows users to query expenses within a specified due date range and optionally filter by text such as expense name or number. This is useful for financial management workflows where you need to retrieve and analyze expense data programmatically, for example:

  • Generating reports of expenses due within a certain period.
  • Automating expense reconciliation by fetching filtered expense lists.
  • Integrating expense data into accounting or ERP systems.

Properties

Name Meaning
Search (Expense) Text to search expenses by name, number, or other identifiers (optional).
Page (Expense) The page number of results to retrieve (pagination).
Page Size (Expense) Number of expense items to return per page.
Due Date (From) Initial due date to filter expenses from (required, format YYYY-MM-DD).
Due Date (Until) Final due date to filter expenses until (required, format YYYY-MM-DD).

Output

The node outputs an array of JSON objects representing the expenses that match the filter criteria. Each object typically contains details about an individual expense such as its name, number, due date, amount, status, and other relevant financial information.

If the API supports binary data related to expenses (e.g., attachments or invoices), the node would handle it accordingly, but based on the provided code and operation, the output is primarily JSON data describing expenses.

Dependencies

  • Requires an active Conta Azul API OAuth2 credential configured in n8n to authenticate requests.
  • Depends on the Conta Azul API service being available and accessible.
  • No additional external dependencies beyond the Conta Azul API and n8n's standard environment.

Troubleshooting

  • Common Issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Providing invalid date formats for the required due date fields may result in errors.
    • Requesting pages beyond the available data range might return empty results.
  • Error Messages:

    • "Operation not supported": This indicates an unsupported operation was selected; ensure "Search Expenses By Filter" is chosen.
    • API errors related to authentication or rate limits should be resolved by verifying credentials and API usage policies.
    • Validation errors for missing required parameters (like due dates) require ensuring all mandatory fields are filled correctly.

Links and References

Discussion