Negocie icon

Negocie

Consume Negocie API
Join our community

Actions6

Overview

This node integrates with the Negocie API to retrieve debt information ("dívidas") associated with a given document identifier. It is designed to fetch outstanding debts from financial institutions or related entities by providing a document number (e.g., CPF/CNPJ). This node is useful in scenarios where users want to automate the retrieval of debt data for credit analysis, debt management, or financial reconciliation.

For example, a user can input a customer's document number and receive detailed debt records linked to that customer, enabling automated workflows for debt collection or financial reporting.

Properties

Name Meaning
Token Bearer token used for authenticating API requests to the Negocie service.
Financeira The financial institution associated with the debt search operation.
Documento The document identifier (e.g., CPF or CNPJ) used to query debts related to that entity.

Note: Although "Financeira" is defined in the properties JSON, it is not explicitly used in the provided execute method code snippet.

Output

The node outputs an array of JSON objects representing the debt information retrieved from the Negocie API for each input item. Each output item corresponds to one input document and contains the debt details as returned by the API under the json field.

No binary data output is produced by this node.

Dependencies

  • Requires access to the Negocie API endpoint.
  • Needs a valid Bearer token for authentication, which must be supplied via the "Token" property.
  • The node depends on internal helper functions (negocieApiRequest) to perform HTTP GET requests to the /dividas/{documento} endpoint.

Troubleshooting

  • Common issues:

    • Invalid or missing Bearer token will cause authentication failures.
    • Incorrect or malformed document identifiers may result in empty or error responses.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • If the API returns an error, the node will throw unless "Continue On Fail" is enabled, in which case it outputs an error object per failed item.
    • Typical errors include authorization errors (401), resource not found (404), or server errors (500).

  • Resolutions:

    • Verify the correctness and validity of the Bearer token.
    • Ensure the document identifier format matches the expected pattern.
    • Check network settings and API availability.

Links and References

Discussion