Actions85
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node interacts with the WaAPI API to retrieve story data based on a specified instance ID. It is useful when you need to fetch detailed information about a particular story from the WaAPI service, for example, to display story content in an application or to process story data further in an automation workflow.
A practical use case would be automating the retrieval of story details by providing the story's unique identifier, enabling integration with other systems such as content management or analytics platforms.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the story instance to retrieve. This property is required and specifies which story the node will fetch from the WaAPI service. |
Output
The node outputs JSON data representing the story details retrieved from the WaAPI API. The structure of this JSON corresponds to the story object returned by the API, typically including fields such as title, content, author, timestamps, and other metadata related to the story instance.
If the API supports binary data (e.g., images or media associated with the story), the node would handle it accordingly, but based on the provided code and properties, the primary output is JSON-formatted story data.
Dependencies
- Requires an active connection to the WaAPI API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for API requests is
https://waapi.app/api/v1. - The node depends on the
@devlikeapro/n8n-openapi-nodepackage for building request properties from the OpenAPI specification.
Troubleshooting
Common issues:
- Invalid or missing story ID: Ensure the "Id" property is set to a valid number corresponding to an existing story.
- Authentication errors: Verify that the API key or token credential is correctly configured and has sufficient permissions.
- Network or connectivity problems: Check internet access and that the WaAPI endpoint is reachable.
Error messages:
- Unauthorized or 401 errors indicate issues with API credentials.
- 404 errors suggest the story ID does not exist or is incorrect.
- Timeout or network errors may require retrying or checking network settings.
Resolving these usually involves verifying input parameters, credentials, and network conditions.
Links and References
- WaAPI Official Website
- WaAPI API Documentation (assumed typical location for API docs)
- n8n Documentation for general guidance on using API nodes and credentials configuration