GateKit icon

GateKit

Universal messaging gateway - send messages across multiple platforms

Actions26

Overview

This node allows updating the role of a member within a specific project in the GateKit system. It is useful for managing user permissions and access control by changing a member's role, such as promoting a member to an admin or demoting them to a viewer. Practical scenarios include adjusting team roles after organizational changes or correcting access levels.

Properties

Name Meaning
User ID of the member to update (userId) The unique identifier of the member whose role you want to update.
New role to assign (role) The new role to assign to the member. Options: admin, member, viewer.
Slug (slug) The project identifier (slug) where the member belongs.
UserId (userId) Duplicate property for the user ID parameter (same as "User ID of the member to update").

Output

The output will contain the JSON response from the API reflecting the updated member information, including their new role and associated metadata. This typically includes confirmation of the update and details about the member's current status in the project.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authenticating with the GateKit API.
  • The node sends a PATCH HTTP request to the endpoint /api/v1/projects/:slug/members/:userId.
  • The base URL and authentication headers are configured via the node credentials.

Troubleshooting

  • Common issues:

    • Incorrect or missing userId or slug parameters will cause the API call to fail.
    • Assigning a role not listed in the allowed options (admin, member, viewer) will result in validation errors.
    • Insufficient permissions of the API key may prevent updating member roles.

  • Error messages:

    • "Member not found": Verify that the userId and slug correspond to an existing member in the project.
    • "Unauthorized" or "Forbidden": Check that the API key has sufficient rights to modify members.
    • "Invalid role value": Ensure the role is one of the allowed options.

Resolving these usually involves verifying input parameters, ensuring correct project slug and user ID, and confirming API key permissions.

Links and References

Discussion