Actions24
- Tag Actions
- Provider Link Actions
- Computer Actions
- Maintenance Actions
- Person Actions
- Tenant Actions
- User Actions
Overview
The node named "ImmyBot" integrates with the ImmyBot API to perform various operations related to its resources. Specifically, for the Computer resource and the Get Agent Status operation, this node retrieves 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 assigned to specific users, such as in IT management or automated system monitoring.
Practical examples include:
- Fetching the current operational status of software agents installed on user machines.
- Monitoring agent health or connectivity for troubleshooting or reporting purposes.
- Integrating agent status data into broader automation workflows within n8n.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user to filter computers by. This property is required to specify 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 other relevant status indicators.
If the node supports binary data output (not indicated in the provided code), it would represent any files or attachments 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 node uses the base URL constructed dynamically from the subdomain provided in 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 requests.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect or missing User ID input will result in errors or empty responses.
- Network connectivity problems to the ImmyBot API endpoint may cause request timeouts or failures.
Error messages:
- Authentication errors typically indicate invalid or expired tokens; re-authenticate or update credentials.
- Validation errors may occur if the User ID is not provided or is not a number; ensure the input is correct.
- API errors returned from ImmyBot should be checked against their documentation for specific causes.
Links and References
- ImmyBot API Documentation (Assumed URL for reference)
- n8n Documentation on Creating Custom Nodes