Negocie icon

Negocie

Consume Negocie API

Overview

The "Negocie" node integrates with the Negocie API to manage financial operations related to debts, payments, agreements, and authentication tokens. It is useful for automating tasks such as querying debt information, processing payments, proposing payment agreements, and obtaining authentication tokens. For example, a user can automate checking outstanding debts for a client, initiate payment transactions, or negotiate payment plans directly within an n8n workflow.

Properties

Name Meaning
Token Bearer Token used for authenticating API requests related to resources like debt, payment, and agreement.

(Note: The provided property list only includes the "Token" property relevant to multiple resources including "divida". Other properties exist in the node but are not detailed here.)

Output

The node outputs JSON data corresponding to the response from the Negocie API for the requested operation. The structure varies depending on the resource and operation:

  • For Debt ("divida") - Consult: Outputs debt details associated with the specified document.
  • For Payment ("pagamento") - Process: Outputs confirmation or status of the payment processed.
  • For Agreement ("acordo") - Propose: Outputs details of the proposed payment agreement.
  • For Authentication ("autenticacao") - Obtain Token: Outputs an authentication token object (with sensitive fields removed).

If the API returns an object, the node removes sensitive fields such as client secrets or passwords before outputting. If no data is returned, it outputs an empty JSON object.

Dependencies

  • Requires access to the Negocie API endpoint.
  • Needs a valid Bearer Token for authorization when accessing debt, payment, and agreement endpoints.
  • For authentication token retrieval, requires client ID and client secret credentials.
  • No explicit external libraries beyond standard n8n workflow dependencies.

Troubleshooting

  • Invalid or missing token: API calls will fail if the Bearer Token is invalid or missing. Ensure the token is correctly set in the input properties.

  • Value validation errors:

    • Payment value must be greater than zero and less than or equal to 1,000,000.
    • Proposal value must be greater than zero and less than or equal to 1,000,000.
    • Number of installments must be between 1 and 60.

    Violations throw clear error messages indicating the constraint.

  • API request failures: Internal server errors or network issues will result in a generic error message advising to check logs.

  • Missing required parameters: The node validates required parameters per operation; missing or invalid parameters cause errors.

Links and References

Discussion