Tiny ERP Auth2 icon

Tiny ERP Auth2

Interact with Tiny ERP API v3 with OAuth2

Actions21

Pedidos → Get Many

AI-generated

Overview

This node interacts with the Tiny ERP API v3 using OAuth2 authentication. Specifically, for the Pedidos resource and the Get Many operation, it retrieves multiple order records from the ERP system. This is useful when you want to fetch a list of orders for reporting, synchronization, or further processing within an automation workflow.

Typical use cases include:

  • Extracting recent orders for analysis or export.
  • Paginating through large sets of orders to process them in batches.
  • Integrating order data into other systems like CRMs or accounting software.

Properties

Name Meaning
Options Collection of optional parameters:
- Limit: Max number of results to return (minimum 1). Default is 50.
- Page: Page number to retrieve (minimum 1). Default is 1.

These options allow controlling pagination when fetching many orders.

Output

The node outputs an array of JSON objects, each representing a single order record retrieved from the Tiny ERP system. The exact structure of each order object depends on the ERP's API response but typically includes fields such as order ID, customer details, order status, items, totals, and dates.

If multiple input items are processed, the output aggregates all resulting orders into a single array.

No binary data output is indicated by the source code.

Dependencies

  • Requires an OAuth2 API credential configured in n8n to authenticate with the Tiny ERP API.
  • Depends on the Tiny ERP API v3 being accessible and the authenticated user having permission to read orders.
  • No additional external dependencies beyond standard n8n modules and the bundled OperationFactory logic.

Troubleshooting

  • Unknown resource error: If the resource parameter is misspelled or unsupported, the node throws an "Unknown resource" error. Ensure the resource name is exactly "pedidos" for this operation.
  • API authentication failures: Errors related to invalid or expired OAuth2 tokens will occur if the credential is misconfigured or revoked. Re-authenticate the credential in n8n.
  • Pagination issues: Setting very high limits or page numbers beyond available data may result in empty responses. Adjust limit and page values accordingly.
  • Continue on Fail: If enabled, errors during execution for individual input items will be captured in the output JSON under an error field instead of stopping the workflow.

Links and References

Discussion