Negocie icon

Negocie

Consume Negocie API
Join our community

Actions6

Overview

This node integrates with the Negocie API to retrieve information related to debts, payments, and agreements. Specifically, for the "Dívida" resource and the "Buscar opções de pagamento" operation, it fetches available payment options associated with a given document identifier (e.g., CPF or CNPJ). This is useful in scenarios where users want to automate the retrieval of payment options for outstanding debts, enabling workflows such as automated debt management, payment processing, or customer notifications about payment possibilities.

Practical examples include:

  • Automatically fetching payment options for a customer's debt record to present them in a CRM.
  • Integrating with financial systems to update payment plans based on available options.
  • Triggering follow-up actions when new payment options become available.

Properties

Name Meaning
Token Bearer Token used for authenticating requests to the Negocie API.

Note: The provided property list only includes the "Token" string input relevant to authentication. Other parameters like "documento" (document identifier) are referenced in the code but not explicitly listed in the provided properties JSON.

Output

The node outputs an array of JSON objects representing the response from the Negocie API for the requested resource and operation. For the "Buscar opções de pagamento" operation under the "Dívida" resource, the output JSON contains details about payment options linked to the specified document.

The exact structure depends on the API response but typically includes fields such as payment methods, amounts, due dates, and other relevant payment option details.

No binary data output is indicated by the source code.

Dependencies

  • Requires access to the Negocie API endpoint.
  • Needs a valid Bearer Token for authentication, supplied via the "Token" property.
  • No explicit mention of additional environment variables or n8n credential types; the token must be provided directly.

Troubleshooting

  • Common Issues:

    • Invalid or missing Bearer Token will cause authentication failures.
    • Incorrect or missing document identifier ("documento") may result in empty or error responses.
    • Network issues or API downtime can cause request failures.

  • Error Handling:

    • The node attempts to continue on failure if configured, returning an error message per item.
    • Common error messages likely relate to authorization errors (401), not found (404) if the document does not exist, or bad request (400) if parameters are invalid.

  • Resolution Tips:

    • Ensure the Bearer Token is current and has necessary permissions.
    • Verify the document identifier format matches expected API requirements.
    • Check network connectivity and API status.

Links and References

Discussion