Nuvem Solution icon

Nuvem Solution

Interact with Nuvem Solution API

Actions120

Veículo Cliente → Get All

AI-generated

Overview

This node integrates with the Nuvem Solution API to perform various operations related to customer vehicles ("Veículo Cliente"). Specifically, the "Get All" operation retrieves a paginated list of customer vehicles, optionally filtered by a date range. This is useful for scenarios where you need to fetch and analyze vehicle data associated with customers, such as fleet management, service scheduling, or reporting on vehicle usage.

Practical examples:

  • Retrieve all customer vehicles added or updated within a specific date range.
  • Paginate through large sets of vehicle data to process or display in batches.
  • Use the vehicle data to trigger follow-up workflows like maintenance reminders or customer notifications.

Properties

Name Meaning
Start At Start date/time filter to limit results to vehicles from this date onwards.
End At End date/time filter to limit results to vehicles up to this date.
Page Page number for pagination (which page of results to retrieve).
Page Size Number of items per page (how many vehicles to return per request).

Output

The output is a JSON array containing the list of customer vehicles matching the specified filters and pagination parameters. Each item in the array represents a vehicle record with its associated details as returned by the Nuvem Solution API.

The structure typically includes fields such as vehicle ID, customer ID, chassis number, registration details, and other relevant vehicle information.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Nuvem Solution API.
  • The node uses the base URL and authentication tokens obtained from these credentials to make authorized HTTP requests.
  • Proper configuration of the API credentials in n8n is necessary before using this node.

Troubleshooting

  • Authentication errors: If the node fails due to authentication issues, verify that the API key credential is correctly configured and has not expired.
  • Invalid date filters: Ensure that the "Start At" and "End At" dates are valid ISO 8601 date-time strings; invalid formats may cause request failures.
  • Pagination issues: Requesting pages beyond the available data will result in empty responses; adjust the page number accordingly.
  • API rate limits: Excessive requests might be throttled by the API; implement delays or reduce request frequency if encountering rate limit errors.
  • Error messages: The node throws errors indicating unsupported operations or unknown resources if misconfigured; double-check that the resource is set to "Veículo Cliente" and operation to "Get All".

Links and References

Discussion