Actions114
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
- Call Actions
- Label Actions
- OpenAI Actions
- N8N Integration Actions
- EvoAI Actions
- Template Actions
- Business Actions
EvoAI → Fetch Sessions
AI-generatedOverview
The EvoAI Fetch Sessions operation in the Evolution API node retrieves session data for a specified bot instance. This is useful for monitoring and managing bot interactions, analyzing session histories, or integrating session data into workflows for further processing or reporting.
Use Case Examples
- Fetch all active sessions for a specific bot to analyze user interactions.
- Retrieve session details to monitor bot performance and user engagement.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the EvoAI instance to target for fetching sessions. |
| Bot ID | The unique identifier of the bot whose sessions are to be fetched. |
Output
JSON
sessionId- Unique identifier of the session.botId- Identifier of the bot associated with the session.startTime- Timestamp when the session started.endTime- Timestamp when the session ended, if applicable.status- Current status of the session (e.g., active, completed).userData- Data related to the user involved in the session.
Dependencies
- Requires an API key credential for the Evolution API to authenticate requests.
Troubleshooting
- Ensure the Instance Name and Bot ID are correctly specified and exist in the EvoAI system.
- Check that the API key credential is valid and has the necessary permissions to access session data.
- If the operation returns an error stating 'Unsupported operation', verify that the resource and operation names are correctly set.
Links
- Evolution API Documentation - Official documentation for the Evolution API, including details on available resources and operations.