GateKit icon

GateKit

Universal messaging gateway - send messages across multiple platforms

Actions26

Overview

The node provides integration with a universal messaging gateway platform, allowing management of project members among other resources. Specifically, the "Remove" operation under the "Members" resource enables users to remove a member from a project by specifying the project identifier and the user ID of the member to be removed.

This operation is useful in scenarios where you need to manage team access dynamically, such as revoking access for users who no longer require it or managing membership based on project roles. For example, if a team member leaves a project, this node can automate their removal from the project's member list.

Properties

Name Meaning
User ID of the member to remove The unique identifier of the user/member to be removed from the project. This is required to specify which member to remove.
Slug The unique slug (identifier) of the project from which the member will be removed. This identifies the target project.
UserId Same as "User ID of the member to remove", representing the user/member's unique identifier.

Note: The properties include two fields named userId with slightly different display names but both represent the user ID parameter required to identify the member to remove.

Output

The output of this operation will be the JSON response returned by the API after attempting to remove the member. Typically, this would include confirmation of successful removal or details about any error encountered.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authentication with the GateKit messaging gateway API.
  • The node uses the base URL provided by the API credentials to send HTTP DELETE requests to the endpoint /api/v1/projects/:slug/members/:userId.
  • Proper configuration of the API URL and valid credentials are necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing slug or userId parameters will cause the request to fail.
    • Insufficient permissions or invalid API credentials may result in authorization errors.
    • Attempting to remove a user who is not a member of the specified project may return a not found or similar error.

  • Error messages:

    • 401 Unauthorized: Check that the API key credential is correctly configured and has sufficient permissions.
    • 404 Not Found: Verify that the project slug and user ID are correct and that the user is indeed a member of the project.
    • 400 Bad Request: Ensure all required parameters (slug, userId) are provided and valid.

Resolving these typically involves verifying input parameters, checking API credentials, and ensuring the user exists in the project.

Links and References

Discussion