Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
This node provides integration with a universal messaging gateway platform, allowing users to manage API keys among other resources. Specifically, the "Revoke" operation under the "ApiKeys" resource enables users to revoke (invalidate) an existing API key within a specified project. This is useful for security management, such as when an API key is compromised or no longer needed.
Practical scenarios include:
- Revoking API keys that are no longer in use to prevent unauthorized access.
- Rotating API keys by revoking old keys after generating new ones.
- Managing access control in multi-project environments by revoking keys per project.
Properties
| Name | Meaning |
|---|---|
| API key ID to revoke | The identifier of the API key that you want to revoke. |
| Project | The project identifier within which the API key exists and should be revoked. |
| KeyId | Another property representing the API key ID to revoke (same as "API key ID to revoke"). |
Note: The properties "API key ID to revoke" and "KeyId" both represent the API key identifier to revoke; they are synonymous in this context.
Output
The node outputs the JSON response from the API after attempting to revoke the specified API key. This typically includes confirmation of the revocation or details about the revoked key. There is no binary data output for this operation.
Dependencies
- Requires an API authentication credential configured in n8n to access the messaging gateway's API.
- The node uses the base URL and authentication headers from the provided credentials.
- The user must specify the project identifier and the API key ID to revoke.
Troubleshooting
- Invalid API Key ID: If the provided API key ID does not exist or is incorrect, the API may return an error indicating the key was not found. Verify the key ID is correct.
- Insufficient Permissions: Revoking an API key requires appropriate permissions on the project. Ensure the API authentication token has rights to manage keys in the specified project.
- Project Not Found: If the project identifier is invalid or does not exist, the request will fail. Confirm the project ID is accurate.
- Network or Authentication Errors: Check that the API credentials are valid and the network connection to the API endpoint is stable.
Links and References
- Refer to the messaging gateway platform's official API documentation for detailed information on API key management and revocation endpoints.
- Consult n8n documentation on how to configure API credentials and use HTTP request nodes if customizations are needed.