Actions24
- Tag Actions
- Provider Link Actions
- Computer Actions
- Maintenance Actions
- Person Actions
- Tenant Actions
- User Actions
Overview
The node "ImmyBot" provides integration with the ImmyBot API, allowing users to interact programmatically with various resources and operations exposed by the service. Specifically, for the Computer resource and the Get User Affinities operation, this node fetches user affinity data related to a specified computer by its ID. This can be useful in scenarios where you want to analyze or report on user interactions or preferences associated with particular computers within an organization.
Practical examples include:
- Retrieving affinity metrics for a given computer to understand user behavior.
- Integrating affinity data into dashboards or workflows for IT management or user experience optimization.
Properties
| Name | Meaning |
|---|---|
| Computer ID | The numeric identifier of the computer for which to retrieve user affinities. |
Output
The node outputs JSON data containing the user affinities related to the specified computer. The exact structure depends on the ImmyBot API response but typically includes affinity scores or related user interaction metrics tied to that computer ID.
If the node supports binary data output (not indicated here), it would represent any files or attachments returned by the API, but this is not evident from the provided code snippet.
Dependencies
- Requires an API key credential for authentication with the ImmyBot service.
- Needs configuration of the subdomain as part of the credentials to construct the base URL for API requests.
- The node uses the ImmyBot OAuth2 API credential type (generic: an API key or OAuth2 token) to authorize requests.
Troubleshooting
- Invalid Computer ID: If the provided computer ID does not exist or is invalid, the API may return an error or empty result. Verify the ID before running the node.
- Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Ensure the API key/token and subdomain are correctly configured.
- Network Issues: Connectivity problems to the ImmyBot API endpoint can cause request failures. Check network access and proxy settings if applicable.
- Unexpected Response Format: If the API changes its response schema, the node's output parsing might fail. Keep the node updated with the latest API version.
Links and References
- ImmyBot API Documentation (hypothetical link based on baseURL pattern)
- n8n documentation on Creating Custom Nodes