Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
This node provides functionality to manage API keys within a project on the MsgCore platform. Specifically, the "Revoke" operation under the "ApiKeys" resource allows users to revoke (delete or disable) an existing API key by its identifier. This is useful for security management, such as when an API key is compromised or no longer needed.
Typical use cases include:
- Revoking access for an API key that has been exposed.
- Cleaning up unused API keys to maintain security hygiene.
- Automating API key lifecycle management in CI/CD pipelines or administrative workflows.
Example: You have an API key used by a third-party service that you want to deactivate immediately. Using this node, you provide the project ID and the API key ID, and the node will revoke that key via the MsgCore API.
Properties
| Name | Meaning |
|---|---|
| API key ID to revoke | The unique identifier of the API key you want to revoke. |
| Project | The identifier of the project where the API key exists. |
| KeyId | Another property representing the API key ID parameter (same as "API key ID to revoke"). |
Note: Both "API key ID to revoke" and "KeyId" represent the same required input — the ID of the API key to revoke.
Output
The node outputs the JSON response from the MsgCore API after attempting to revoke the specified API key. This typically includes confirmation of the revocation or details about the revoked key.
No binary data output is involved in this operation.
Dependencies
- Requires an active MsgCore API credential with appropriate permissions to manage API keys.
- The node uses the MsgCore API endpoint structured as
/api/v1/projects/{project}/keys/{keyId}with HTTP DELETE method to perform the revocation. - The user must configure the MsgCore API URL and authentication credentials in n8n.
Troubleshooting
- Invalid API key ID: If the provided API key ID does not exist or is malformed, the API may return an error indicating the key was not found. Verify the key ID is correct.
- Insufficient permissions: If the API credential lacks permission to revoke keys, the request will fail with an authorization error. Ensure the credential has the necessary rights.
- Project not found: Providing an incorrect project identifier will result in an error. Confirm the project ID is valid.
- Network issues: Connectivity problems to the MsgCore API endpoint can cause failures. Check network access and API URL configuration.
Links and References
- MsgCore API Documentation (general reference for API key management endpoints)
- n8n Docs - Creating Custom Nodes (for understanding node implementation concepts)