Actions26
Overview
This node integrates with the GateKit API to manage project members. Specifically, the "Members" resource with the "List" operation allows users to retrieve a list of all members associated with a specific project identified by its slug. This is useful for scenarios where you need to audit or display project membership, manage access control, or synchronize member data with other systems.
Practical examples include:
- Fetching all members of a project to display in a dashboard.
- Automating notifications or role updates based on current project members.
- Integrating with external user management systems to keep member lists in sync.
Properties
| Name | Meaning |
|---|---|
| Slug | The unique identifier (slug) of the project whose members you want to list. This is a required string parameter. |
Output
The output of this operation is the JSON response from the GateKit API endpoint that lists project members. It typically contains an array of member objects, each representing a user associated with the project, including details such as user ID, email, role, and other relevant metadata.
No binary data is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the GateKit API.
- The node uses the base URL provided by the API credentials to send HTTP GET requests to the endpoint
/api/v1/projects/:slug/members. - Proper configuration of the API URL and authentication token in n8n credentials is necessary.
Troubleshooting
- Common issues:
- Invalid or missing slug parameter will cause the request to fail.
- Authentication errors if the API key credential is not set up correctly.
- Network or connectivity issues preventing access to the GateKit API.
- Error messages:
- Unauthorized or 401 errors indicate problems with API credentials; verify and update them.
- 404 Not Found may indicate the project slug does not exist.
- 400 Bad Request could mean malformed parameters; ensure the slug is correctly formatted.
- Resolution:
- Double-check the slug value for correctness.
- Confirm API credentials are valid and have sufficient permissions.
- Check network connectivity and API availability.
Links and References
- GateKit API Documentation (hypothetical link, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes.