Actions12
- Sesiones Actions
- Mensajería Actions
- Chats y Mensajes Actions
Overview
This node, named "Expertos en IA," provides an interface to interact with the secure API of Expertos en IA. It supports multiple resources including messaging, chats, and sessions. Specifically for the Sesiones resource with the operation Obtener Información de Sesión, the node retrieves detailed information about a particular session by its name.
This functionality is useful in scenarios where you need to monitor or manage active sessions programmatically, such as checking session status, metadata, or other session-related details within automated workflows.
Practical example:
You might use this node to fetch the current state or configuration of a user session before performing further actions like sending messages or logging out the session.
Properties
| Name | Meaning |
|---|---|
| Nombre de la Sesión | The name identifier of the session to retrieve information from. |
Output
The output is a JSON object containing the session information returned by the Expertos en IA API. The exact structure depends on the API response but typically includes details about the session identified by the provided session name.
- The
jsonfield contains the session data. - If an error occurs, the output will include an
errorobject with message and stack trace (if configured to continue on failure). - No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authentication with the Expertos en IA API.
- The node makes HTTP requests to
https://api.expertosenia.com. - Proper configuration of the API key credential in n8n is necessary.
- The session name must correspond to an existing session recognized by the API.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing a non-existent session name will likely result in an error or empty response.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Operación no válida."— This indicates an invalid operation was selected; ensure the operation matches the resource.- API errors returned from the server will be included in the output under the
errorproperty if "Continue On Fail" is enabled.
Resolutions:
- Verify that the API key credential is correctly set up and has proper permissions.
- Confirm the session name exists and is spelled correctly.
- Check network access and firewall settings to allow outbound HTTPS requests to the API endpoint.