Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
This node integrates with the GateKit API to manage project members. Specifically, the "Add" operation under the "Members" resource allows you to add a new member to a specified project by providing their email and assigning them a role. This is useful in scenarios where you want to programmatically manage access control and collaboration within projects, such as onboarding new team members or automating user management workflows.
Practical examples:
- Automatically adding a new user to a project when they sign up on your platform.
- Assigning specific roles (owner, admin, member, viewer) to users based on their responsibilities.
- Integrating with HR systems to sync project memberships.
Properties
| Name | Meaning |
|---|---|
| Email of user to add | The email address of the user to be added as a member to the project. |
| Role to assign to member | The role assigned to the new member. Options: owner, admin, member, viewer. |
| Project | Identifier of the project to which the member will be added. Defaults to "default". |
Output
The node outputs the JSON response from the GateKit API after attempting to add the member. This typically includes details about the newly added member, such as their user ID, email, assigned role, and possibly status or metadata related to the membership.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the GateKit API.
- The node expects the base URL for the API to be configured via credentials.
- The project identifier must be provided to specify the target project.
Troubleshooting
Common issues:
- Invalid or missing API authentication token can cause authorization errors.
- Providing an invalid or non-existent project identifier will result in failure to add the member.
- Supplying an improperly formatted email or a user that already exists may cause errors.
- Assigning a role outside the allowed options (owner, admin, member, viewer) will fail.
Error messages and resolutions:
- 401 Unauthorized: Check that the API key credential is correctly set and has sufficient permissions.
- 404 Not Found: Verify the project identifier is correct and the project exists.
- 400 Bad Request: Ensure the email is valid and the role is one of the supported values.
- 409 Conflict: The user might already be a member; check existing memberships before adding.
Links and References
- GateKit API Documentation (generic link, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding API calls
- Best practices for managing project members and roles in collaborative platforms