ImmyBot icon

ImmyBot

ImmyBot Node

Actions24

Overview

The node is designed to update user information within the ImmyBot system. It allows modifying various user attributes such as admin privileges, tenant association, and management access rights. This node is useful in scenarios where user roles or permissions need to be adjusted dynamically, for example, promoting a user to an admin role, changing their tenant affiliation, or updating their deployment management capabilities.

Practical examples include:

  • Updating a user's admin status after a promotion.
  • Changing the tenant ID when a user moves between organizational units.
  • Granting or revoking cross-tenant deployment management rights.

Properties

Name Meaning
Person ID (Optional) The unique identifier of the person to configure as a user.
Is Admin Whether the user should have administrative privileges.
Tenant ID The identifier of the tenant this user belongs to.
Can Manage Cross-Tenant Deployments Whether the user can manage deployments across multiple tenants (only applicable if not admin).
Has Management Access Whether the user has management access rights.

Output

The node outputs JSON data representing the updated user object after the operation completes successfully. This typically includes the user's updated properties such as admin status, tenant ID, and access rights. There is no indication that the node outputs binary data.

Dependencies

  • Requires an API key credential for authentication with the ImmyBot service.
  • The base URL for API requests is constructed dynamically using the subdomain from the credentials.
  • The node expects the ImmyBot API to be accessible at https://{subdomain}.immy.bot/api/v1.

Troubleshooting

  • Missing or invalid Person ID: Since the Person ID is required to identify which user to update, omitting it or providing an incorrect value will likely cause errors. Ensure the correct numeric ID is provided.
  • Insufficient permissions: Attempting to update user properties without proper API credentials or insufficient privileges may result in authorization errors.
  • Invalid tenant ID: Providing a tenant ID that does not exist or is not accessible by the authenticated user could cause failures.
  • Conflicting property values: For example, setting both admin privileges and cross-tenant deployment management flags inconsistently might lead to unexpected behavior; note that "Can Manage Cross-Tenant Deployments" only applies if the user is not an admin.

Links and References

Discussion