Actions26
- Product Actions
- Order Actions
- Customer Actions
- Category Actions
- Stock Actions
Order → Update State
AI-generatedOverview
The node integrates with the PrestaShop API to update the state of an existing order. It allows users to change the status of an order, such as marking it as "Shipped," "Delivered," or "Canceled." This is useful in e-commerce workflows where order management automation is needed, for example:
- Automatically updating order status after payment confirmation.
- Changing order states based on shipping updates.
- Managing refunds or cancellations programmatically.
By automating these updates, businesses can streamline order processing and improve customer communication.
Properties
| Name | Meaning |
|---|---|
| Order ID | The unique numeric identifier of the order to update. |
| Order State | The new state to assign to the order. Options include: Awaiting Check Payment, Payment Accepted, Preparation in Progress, Shipped, Delivered, Canceled, Refunded, Payment Error, On Backorder (Paid), On Backorder (Not Paid). |
| Advanced Options | A collection of optional settings: - Output Format: Choose between JSON (recommended) or XML response format. - Language ID: Numeric ID to filter localized fields (default 1). - Display Fields: Select full data or custom fields. - Custom Fields: Comma-separated list of specific fields to return. - Shop Context: Define scope as all shops, a specific shop, or a shop group. - Shop ID: Numeric ID of the specific shop (if applicable). - Shop Group ID: Numeric ID of the shop group (if applicable). - Enable Debug Mode: Include debug info like URL, method, and parameters in the response. |
Output
The node outputs the updated order information in the chosen format (JSON by default, or XML if selected). The json output contains the order details reflecting the new state and any other requested fields. If debug mode is enabled, additional metadata about the API request is included.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a PrestaShop instance via its REST API.
- Needs an API key credential configured in n8n for authentication.
- The node depends on network access to the PrestaShop server.
- Optional: Multishop context requires correct shop or shop group IDs.
Troubleshooting
Common Issues:
- Invalid or missing Order ID will cause the update to fail.
- Incorrect API credentials or insufficient permissions may result in authentication errors.
- Specifying invalid order states or unsupported language/shop IDs can cause errors.
- Network connectivity problems to the PrestaShop server will prevent execution.
Error Messages:
- "Order not found": Verify the Order ID exists in PrestaShop.
- "Authentication failed": Check API key validity and permissions.
- "Invalid parameter": Review input properties for correct values and formats.
- Timeout or network errors: Ensure the PrestaShop server is reachable from n8n.
Enabling debug mode can help diagnose issues by providing detailed request and response information.