Actions19
- Customer Actions
- Customer Catalog Actions
- Customer Platform Actions
- Order Actions
- Platform Actions
- Receivable Charge Actions
- Subscription Actions
- Tracking Actions
Overview
The "Place Order" operation in the Sherweb node allows users to create and submit an order through either the Service Provider API or the Distributor API. This operation is useful for automating order placement workflows, such as submitting customer orders programmatically based on cart contents. Practical examples include integrating e-commerce platforms with Sherweb's ordering system to automatically place orders when customers check out, or syncing orders from external systems into Sherweb.
Properties
| Name | Meaning |
|---|---|
| API Type | Selects which API to use for the request: "Service Provider API" or "Distributor API". |
| Customer ID | The unique identifier of the customer placing the order. |
| Cart Items | A JSON array representing the items to order, each with SKU and quantity. |
| Ordered By | The name of the person or entity who is placing the order. |
Output
The node outputs a JSON object containing the response from the Sherweb API after placing the order. This typically includes details about the created order such as order ID, status, and any relevant metadata returned by the API. If the API supports it, binary data output is not indicated for this operation.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials.
- Needs a subscription key provided in the node credentials to authorize requests.
- The base URL for API calls is
https://api.sherweb.com. - Proper configuration of the API type (Service Provider or Distributor) is necessary to route requests correctly.
Troubleshooting
- Invalid Customer ID: Ensure the Customer ID exists and is correct; otherwise, the API will reject the order.
- Malformed Cart Items JSON: The cart items must be a valid JSON array with correct SKU and quantity fields.
- Authentication Errors: Verify that the OAuth2 credentials and subscription key are valid and have not expired.
- API Type Mismatch: Selecting the wrong API type may cause the request to fail if the resource or operation is unsupported.
- Network Issues: Check connectivity to
https://api.sherweb.comand ensure no firewall blocks the requests.
Links and References
- Sherweb API Documentation (for detailed API endpoints and payload structures)
- n8n OAuth2 Credential Setup (for configuring OAuth2 credentials)
- JSON Syntax Guide (to validate cart items input)