Actions26
Overview
This node integrates with the GateKit API to manage API keys within a specified project. The "List" operation for the "ApiKeys" resource retrieves all API keys associated with a given project. This is useful for administrators or developers who need to audit, monitor, or manage API keys programmatically.
Typical use cases include:
- Retrieving all active API keys for a project to review permissions.
- Automating security audits by listing API keys regularly.
- Integrating with other systems that require knowledge of existing API keys.
For example, you might use this node to fetch all API keys for your "default" project and then filter or display them in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Project Slug | Project identifier to operate on (string). This specifies which project's API keys to list. |
Output
The node outputs JSON data containing the list of API keys for the specified project. Each item in the output typically includes details about an API key such as its ID, name, scopes, creation date, expiration, and status.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the GateKit API.
- The node expects the base URL of the GateKit API to be configured in the credentials.
- Network access to the GateKit API endpoint is necessary.
Troubleshooting
- Authentication errors: Ensure that the API key credential is valid and has sufficient permissions to list API keys.
- Invalid project slug: If the project slug does not exist or is misspelled, the API will return an error. Verify the slug value.
- Network issues: Connectivity problems can cause request failures. Check network settings and API availability.
- Empty results: If no API keys are returned, confirm that the project actually has API keys created.
Links and References
- GateKit API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding how API calls are made in custom nodes