GateKit icon

GateKit

Universal messaging gateway - send messages across multiple platforms

Actions51

Overview

The "Update Member" operation in the Members resource allows you to change the role of an existing member within a specified project. This is useful for managing user permissions and access levels dynamically, such as promoting a member to admin or restricting their access by assigning a viewer role.

Practical examples:

  • Updating a team member's role from "member" to "admin" to grant them higher privileges.
  • Changing a user's role to "viewer" to limit their access to read-only.
  • Adjusting roles as project responsibilities evolve without removing and re-adding members.

Properties

Name Meaning
User ID of the member to update (userId) The unique identifier of the user whose role you want to update.
New role to assign (role) The new role to assign to the member. Options: admin, member, viewer.
Project (project) Identifier of the project where the member belongs. Defaults to "default".

Output

The node outputs the JSON response returned by the API after updating the member's role. This typically includes details about the updated member, such as their user ID, assigned role, and possibly other metadata related to the membership in the project.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests against the GateKit API.
  • The node sends a PATCH HTTP request to the endpoint /api/v1/projects/{project}/members/{userId} with query parameters specifying the new role.
  • The project parameter must correspond to an existing project identifier in the system.

Troubleshooting

  • Invalid User ID: If the provided user ID does not exist in the project, the API will likely return an error indicating the member was not found. Verify the user ID is correct.
  • Insufficient Permissions: Attempting to update roles without proper API credentials or insufficient privileges may result in authorization errors.
  • Invalid Role Value: Assigning a role outside the allowed options (admin, member, viewer) will cause validation errors.
  • Project Not Found: Specifying a non-existent project identifier will lead to errors; ensure the project exists and the identifier is correct.

To resolve these issues:

  • Double-check all input values for correctness.
  • Ensure your API key has sufficient permissions.
  • Confirm the project and user exist in the system before attempting updates.

Links and References

Discussion