Nuvem SolutionInstall

Overview

This node integrates with the Nuvem Solution API to perform various operations across multiple resources. Specifically, for the "Veículo Próprio" resource and the "Get By Filial" operation, it retrieves a list of own vehicles associated with a specific branch or company (filial). This is useful in scenarios where you need to manage or analyze the fleet of vehicles owned by a company branch, such as for logistics, maintenance scheduling, or asset tracking.

Practical example:
If a company wants to fetch all its own vehicles registered under a particular branch to monitor their status or assign tasks, this node operation can be used to query that data directly from the Nuvem Solution system.

Properties

Output

The output is a JSON array containing the details of the own vehicles associated with the specified branch. Each item in the array represents a vehicle object with properties as returned by the Nuvem Solution API endpoint /erp/oficina/veiculosProprios/filial/{filialId}.

The exact structure of each vehicle object depends on the API response but typically includes vehicle identifiers, license plate, model, status, and other relevant metadata.

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authenticating with the Nuvem Solution API.
• The node expects credentials providing:
  • Base URL of the API
  • Software key
  • Secret
  • User ID
  • User key
• These credentials must be configured in n8n prior to using the node.
• The node uses HTTP requests to communicate with the Nuvem Solution REST API.

Troubleshooting

• Authentication errors:
  If authentication fails, ensure that the API credentials (software key, secret, user ID, user key) are correct and have not expired. The node caches tokens but will re-authenticate if needed.

• Invalid Filial ID:
  Providing an invalid or non-existent Filial ID may result in empty results or API errors. Verify the Filial ID before running the node.

• Network issues:
  Connectivity problems or incorrect base URL configuration can cause request failures. Confirm network access and correct API endpoint URLs.

• Unsupported operation error:
  If the operation or resource is misspelled or unsupported, the node throws an error indicating the unknown resource or operation.

Links and References

• Nuvem Solution API Documentation (Assumed official API docs; replace with actual link if available)
• n8n Documentation: Creating Custom Nodes
• REST API Concepts: RESTful API Design

Summary of the execute() logic for "Veículo Próprio" - "Get By Filial"

• The node reads the input data items.
• For each item, it extracts the resource ("veiculoProprio") and operation ("getByFilial").
• It retrieves the filialId parameter from the node inputs.
• It constructs an HTTP GET request to the endpoint:
  /erp/oficina/veiculosProprios/filial/{filialId}
• The request includes an Authorization header with a Bearer token obtained via prior authentication.
• The response JSON is collected and returned as the node's output.

This design allows users to fetch own vehicles filtered by branch efficiently within n8n workflows.