Nuvem Solution icon

Nuvem Solution

Interact with Nuvem Solution API

Actions120

Pedido → Listar Pedidos

AI-generated

Overview

The "Pedido" resource with the "Listar Pedidos" operation allows users to retrieve a paginated list of orders from the Nuvem Solution API. This node is useful for scenarios where you need to fetch and process order data within an automation workflow, such as generating reports, syncing orders with other systems, or monitoring order statuses over a specific time range.

For example, a business could use this node to:

  • List all orders created between two dates.
  • Paginate through large sets of orders to process them in batches.
  • Integrate order data into CRM or ERP systems for further analysis.

Properties

Name Meaning
Start At Start date filter: Only orders created on or after this date will be listed.
End At End date filter: Only orders created on or before this date will be listed.
Page Page number for pagination: Specifies which page of results to retrieve (default 1).
Page Size Number of items per page: Controls how many orders are returned per page (default 10).

Output

The output is a JSON array containing the list of orders matching the specified filters and pagination parameters. Each item in the array represents an individual order object with its associated details as provided by the Nuvem Solution API.

The structure of each order object depends on the API response but typically includes fields such as order ID, customer information, order date, status, and other relevant order metadata.

This node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Nuvem Solution API.
  • The node uses bearer token authentication obtained via the configured credentials.
  • The base URL for the API and authentication tokens are managed internally by the node.
  • No additional external dependencies beyond the Nuvem Solution API and valid credentials.

Troubleshooting

  • Authentication failures: If the node throws errors related to authentication, verify that the API key credential is correctly configured and has not expired.
  • Invalid date formats: Ensure that the "Start At" and "End At" properties are set using valid datetime values; invalid formats may cause request failures.
  • Pagination issues: Requesting pages beyond the available range may return empty results; adjust the "Page" and "Page Size" accordingly.
  • API rate limits: Excessive requests might be throttled by the API; consider adding delays or handling retries in your workflow.
  • Error messages: The node throws descriptive errors if unsupported operations or resources are requested, or if required parameters are missing.

Links and References


If you need details about other operations or resources, feel free to ask!

Discussion