Negocie

Overview

This node integrates with the Negocie API to manage financial operations related to debts, payments, agreements, and authentication. Specifically, for the "Pagamento" resource and the "Emitir segunda via de boleto" operation (which corresponds to processing payments), it allows users to initiate payment transactions by providing necessary details such as a document identifier and payment amount.

Common scenarios include:

• Automating payment processing workflows where a second copy of a payment slip (boleto) needs to be issued.
• Integrating payment management into larger financial automation pipelines.
• Validating and submitting payment requests programmatically.

Example use case:

• A company wants to automatically issue a second copy of a boleto for a customer who lost the original, by triggering this node with the customer's document ID and payment amount.

Properties

Name	Meaning
Token	Bearer Token used for API authentication. Required to authorize requests to Negocie API.

Note: Although the user provided only the "Token" property explicitly, the code also expects other parameters like documento (document identifier) and valor (payment amount) when processing payments, which are validated internally but not listed in the provided properties JSON.

Output

The node outputs an array of JSON objects representing the response from the Negocie API after executing the requested operation.

For the "Emitir segunda via de boleto" (payment processing) operation, the output JSON typically contains details about the payment transaction, such as confirmation data or boleto information.

If the API returns sensitive fields like client secrets or passwords, these are removed from the output before returning.

No binary data output is indicated in the source code.

Dependencies

• Requires access to the Negocie API endpoint.
• Needs a valid Bearer Token for authorization, which must be supplied as an input property.
• The node uses internal helper functions (negocieApiRequest) to make HTTP requests to the API.
• No additional external services or environment variables are explicitly required beyond the token.

Troubleshooting

• Invalid or missing token: If the Bearer Token is incorrect or missing, the API will reject requests. Ensure the token is valid and correctly passed.
• Invalid payment amount: The node enforces that the payment amount (valor) must be greater than zero and less than or equal to 1,000,000. Providing values outside this range will cause an error.
• Missing document identifier: The document parameter is mandatory for payment operations; omitting it will cause validation errors.
• API errors: Any server-side errors from the Negocie API will be surfaced as node errors. Check logs for detailed messages.
• General internal errors: Unexpected exceptions are caught and reported as internal server errors with a prompt to check logs.

Links and References

• Negocie API Documentation (hypothetical link, replace with actual if available)
• n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/