Actions21
Pedidos → Create
AI-generatedOverview
This node integrates with the Tiny ERP API v3 using OAuth2 authentication to manage various business resources. Specifically, for the Pedidos (Orders) resource with the Create operation, it allows users to create new orders in the Tiny ERP system by providing order details such as customer ID, total value, and observations.
Typical use cases include automating order creation workflows where order data from other systems or forms is pushed into Tiny ERP for processing, invoicing, or inventory management. For example, after receiving an order on an e-commerce platform, this node can be used to automatically create a corresponding order record in Tiny ERP.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional fields to specify additional order details: |
| - Customer ID | The identifier of the customer placing the order (string). |
| - Total Value | The total monetary value of the order (number). |
| - Observation | Any notes or comments related to the order (string). |
Output
The node outputs JSON objects representing the created order(s) as returned by the Tiny ERP API. Each output item contains a json field with the order data structure, which typically includes identifiers, status, timestamps, and any other relevant order information provided by the API response.
No binary data output is produced by this node.
Dependencies
- Requires an OAuth2 API credential configured in n8n to authenticate requests against the Tiny ERP API.
- Depends on the Tiny ERP API v3 being accessible and the authenticated user having permissions to create orders.
- Uses an internal OperationFactory to handle resource-specific operations dynamically.
Troubleshooting
- Unknown resource error: If the node throws an error like "Unknown resource: pedidos," ensure that the resource name is correctly set to "pedidos" and supported by the node version.
- Authentication failures: Verify that the OAuth2 credentials are valid and have not expired.
- API errors during creation: Errors returned from the Tiny ERP API (e.g., invalid customer ID, missing required fields) will be surfaced. Check the error message in the output JSON under the
errorkey if "Continue On Fail" is enabled. - Empty or malformed input: Ensure that the input data to the node is properly structured and that required fields are provided.
Links and References
- Tiny ERP API Documentation (general reference for API endpoints and data structures)
- n8n OAuth2 Credential Setup (guide on configuring OAuth2 credentials in n8n)