Actions20
- Вопросы Actions
- Отзывы Actions
- Шаблоны Ответов Actions
- Чат С Покупателями Actions
- Возвраты Покупателями Actions
Overview
This node interacts with the Wildberries (WB) API to retrieve seller event data from the "Чат С Покупателями" (Chat with Customers) resource. Specifically, the "Get Seller Events" operation fetches events related to a seller's interactions or communications with customers. This can be useful for sellers who want to monitor and analyze their customer engagement activities directly within their n8n workflows.
Practical examples include:
- Automatically fetching new chat events to trigger follow-up actions.
- Aggregating customer communication data for reporting or analytics.
- Integrating seller event data into CRM or support systems.
Properties
| Name | Meaning |
|---|---|
| Next | Paginator parameter indicating the starting point to fetch the next batch of data. It expects a Unix timestamp with milliseconds precision. This allows incremental retrieval of seller events starting from a specific moment in time. |
Output
The node outputs JSON data representing the seller events retrieved from the WB API. The structure typically includes details about each event such as timestamps, event types, and associated metadata relevant to seller-customer communications.
If binary data is returned by the API (not indicated here), it would represent attachments or media related to the events, but this node primarily handles JSON event data.
Dependencies
- Requires an API key credential for authenticating with the Wildberries API.
- The node depends on the WB API endpoint defined in the bundled swagger specification.
- No additional external services are required beyond the WB API.
- Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing an invalid "Next" timestamp may result in empty responses or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- Rate limit errors suggest too many requests in a short period; implement retry logic or increase intervals.
- Malformed request errors may occur if the "Next" parameter is not a valid Unix timestamp with milliseconds; ensure correct formatting.
Links and References
- Wildberries API Documentation (general reference for WB API)
- n8n documentation on creating custom nodes
- Unix timestamp format explanation: https://www.unixtimestamp.com/
Note: The node's internal implementation uses a swagger-based properties builder and sets default headers for JSON content type. The actual API call logic is abstracted away in the base classes and swagger definitions included in the bundle.