Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node allows you to delete a specific API key by its unique identifier. It is useful in scenarios where you need to revoke access or manage API keys programmatically, such as removing outdated or compromised keys from your system.
For example, if you have an automated workflow that manages user access, this node can be used to delete an API key when a user is deactivated or their permissions change.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the API key object to delete. This is required to specify which API key should be removed. |
Output
The node outputs JSON data representing the result of the deletion operation. Typically, this will include confirmation that the API key was successfully deleted or details about any error encountered.
If the node supports binary data output, it would generally relate to response payloads, but based on the provided code and context, the output is JSON only.
Dependencies
- Requires an API authentication token or API key credential to authorize requests.
- Depends on the external Twenty API service endpoint configured via credentials.
- The base URL for API requests is dynamically set from the node's credentials.
Troubleshooting
- Missing or invalid Id: If the "Id" property is not provided or incorrect, the API will likely return an error indicating the resource could not be found. Ensure the correct API key ID is supplied.
- Authentication errors: If the API key credential is missing or invalid, the request will fail with an authorization error. Verify that the API credentials are correctly configured.
- Network or API errors: Issues connecting to the external API or server errors may cause failures. Check network connectivity and API service status.
- Permission issues: The authenticated user must have permission to delete API keys; otherwise, the operation will be denied.
Links and References
- Twenty API Documentation (Assumed based on the node name; replace with actual link)
- n8n documentation on API Key Management