Actions24
- Computer Actions
- Maintenance Actions
- Person Actions
- Provider Link Actions
- Tag Actions
- Tenant Actions
- User Actions
Overview
The node named "ImmyBot" integrates with the ImmyBot API, allowing users to interact with various resources and operations provided by the service. Specifically, for the Computer resource and the Get Agent Status operation, this node fetches the status of an agent associated with a computer filtered by a user ID. This can be useful in scenarios where you need to monitor or audit the status of agents running on computers linked to specific users.
Practical examples include:
- Retrieving the current operational status of monitoring agents installed on user computers.
- Automating alerts or workflows based on agent health or connectivity.
- Integrating agent status data into broader IT management dashboards.
Properties
| Name | Meaning |
|---|---|
| User ID | The user ID to filter computers by. It is a required numeric input that specifies which user's computers' agent status should be retrieved. |
Output
The node outputs JSON data representing the agent status information for the specified user’s computers. The exact structure depends on the ImmyBot API response but typically includes details such as agent state, last check-in time, and any relevant metadata about the agent's condition.
If the node supports binary data output (not evident from the provided code), it would likely represent files or logs related to the agent status, but no such indication is present here.
Dependencies
- Requires an API key credential for authentication with the ImmyBot service.
- The base URL for API requests is dynamically constructed using a subdomain value from the credentials.
- The node expects the ImmyBot API to be accessible at
https://{subdomain}.immy.bot/api/v1. - Proper configuration of the OAuth2 API credential is necessary for successful communication.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect or missing User ID input will prevent the node from retrieving the desired data.
- Network connectivity problems or incorrect subdomain configuration may lead to request failures.
Error messages:
- Authentication errors typically indicate invalid or expired API tokens; re-authenticate or update credentials.
- Validation errors may occur if the User ID is not provided or is of the wrong type; ensure it is a valid number.
- HTTP errors from the API (e.g., 404 or 500) suggest issues with the endpoint or server; verify the resource and operation parameters.
Links and References
- ImmyBot API Documentation (Assumed official API docs for further details)
- n8n documentation on Creating Custom Nodes