Overview
The node provides integration with an ABMS (presumably a backend management system) API, allowing users to perform various operations such as creating, deleting, describing elements, querying data, logging in, and logging out. The "Logout" operation specifically is intended to terminate a session established with the ABMS system.
However, the "Logout" operation is not implemented in this node's current version. Attempting to use the Logout operation will result in an error indicating that it is not supported.
This node would be beneficial in scenarios where automated interaction with the ABMS API is required, such as managing records, querying data, or handling sessions programmatically within n8n workflows.
Practical example:
- A workflow logs into the ABMS system, performs queries or updates on elements, and then ideally logs out to close the session. However, since logout is not implemented, the session termination must be handled outside this node or by other means.
Properties
| Name | Meaning |
|---|---|
| Session Name | The name of the session to use for the operation. This is required for all operations except Login. It should be obtained from a successful Login operation. |
Note: For the Logout operation, only the "Session Name" property is relevant and required.
Output
The node returns the JSON response from the ABMS API corresponding to the requested operation. The structure depends on the operation performed but generally includes success status, results, or error messages.
For the Logout operation, since it is not implemented, no output is produced; instead, an error is thrown.
No binary data output is involved.
Dependencies
- Requires an API key credential for authentication with the ABMS API.
- The node uses HTTP requests to communicate with the ABMS webservice endpoint (
/webservice.php). - The base URL and credentials (username, access key) must be configured in the node's credentials.
Troubleshooting
Error: "logout operation is not implemented."
This error occurs because the Logout operation has not been coded in the node. To resolve, either avoid using the Logout operation or implement custom logic outside this node to handle session termination.General API errors:
Errors returned from the ABMS API (e.g., invalid session, authentication failure) will be passed through. Check that the session name is correct and that credentials are valid.Missing Session Name:
For operations other than Login, the session name must be provided. Omitting it will cause errors.
Links and References
- No external links are provided in the source code.
- Refer to the ABMS API documentation for details on session management and available operations.