Actions24
- Computer Actions
- Maintenance Actions
- Person Actions
- Provider Link Actions
- Tag Actions
- Tenant Actions
- User Actions
Overview
This node, named "ImmyBot," integrates with the ImmyBot API to manage various resources. Specifically, for the User resource, it supports deleting a user by their ID. This operation is useful in scenarios where you need to programmatically remove users (technicians) from your system, such as automating cleanup of inactive or obsolete accounts.
A practical example would be an automated workflow that deletes technician accounts after they leave an organization or when their access needs to be revoked.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric ID of the technician to delete |
Note: The property applies when the resource is "users" and the operation is "deleteTechnician".
Output
The node outputs data on its main output channel. The json output field will contain the response from the ImmyBot API after attempting to delete the specified user. Typically, this will include confirmation of deletion or error details if the operation failed.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authentication with the ImmyBot service.
- The node uses OAuth2-based credentials to authenticate requests.
- The base URL for API requests is dynamically constructed using the subdomain provided in the credentials.
- The node expects the ImmyBot API to be accessible at
https://{subdomain}.immy.bot/api/v1.
Troubleshooting
Common issues:
- Invalid or missing User ID: Ensure the User ID is provided and is a valid number.
- Authentication errors: Verify that the OAuth2 credentials are correctly configured and have the necessary permissions.
- Network or connectivity problems: Confirm that the subdomain and API endpoint are reachable.
Error messages:
- Authorization failures typically indicate invalid or expired credentials.
- Not found errors may occur if the User ID does not exist.
- Validation errors can happen if the User ID format is incorrect.
Resolving these usually involves checking input parameters, refreshing credentials, and verifying API availability.
Links and References
- ImmyBot API Documentation (Assumed link based on context; replace with actual if available)