Overview
This node triggers workflows based on new orders or order status updates from Zid, an e-commerce platform. It periodically polls the Zid API to check for new or updated orders and emits the order data to the workflow. This is useful for automating order processing, notifications, or integrations with other systems whenever an order event occurs.
Use Case Examples
- Trigger a workflow every 5 minutes to process new orders from Zid.
- Trigger a workflow when an order status is updated to update inventory or notify customers.
Properties
| Name | Meaning |
|---|---|
| Trigger On | Specifies the event that triggers the workflow, either when a new order is created or when an order status is updated. |
| Polling Interval (minutes) | How often the node checks for new or updated orders, in minutes. |
| Order Status Filter | Optional filter to only trigger on orders with a specific status. Only applicable when triggering on new orders. |
| Limit | Maximum number of orders to fetch per poll, limiting the batch size of orders processed each time. |
Output
JSON
id- Unique identifier of the order.created_at- Timestamp when the order was created.status- Current status of the order.- ``
*
* `` - Other order details as returned by the Zid API.
Dependencies
- Requires OAuth2 credentials for Zid API access.
Troubleshooting
- Ensure OAuth2 credentials are correctly configured; missing tokens will cause errors.
- If no orders are fetched, check the polling interval and status filter settings.
- API request failures will emit an error object with a message and timestamp.