Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
This node allows you to delete an identity and all its associated aliases within a specified project in the GateKit platform. It is useful for managing user identities by removing obsolete or unwanted identities from your project.
Typical use cases include:
- Cleaning up identities that are no longer active or relevant.
- Managing user data privacy by deleting user identities upon request.
- Automating identity lifecycle management in messaging or platform integrations.
For example, if you have a user identity linked to multiple messaging platforms and want to remove it completely from your project, this node operation will perform that deletion.
Properties
| Name | Meaning |
|---|---|
| Identity ID to delete | The unique identifier of the identity you want to delete. |
| Project | The identifier of the project where the identity exists. Defaults to "default". |
| Id | Alias for the identity ID parameter (same as "Identity ID to delete"). |
Output
The output JSON contains the response from the API after attempting to delete the specified identity. Typically, this will confirm successful deletion or provide error details if the operation failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate with the GateKit API.
- The node makes HTTP DELETE requests to the GateKit API endpoint corresponding to the project and identity ID.
- Ensure the API URL and credentials are properly set in the node's credentials configuration.
Troubleshooting
Common issues:
- Providing an invalid or non-existent identity ID will result in an error.
- Insufficient permissions or incorrect API credentials may cause authorization failures.
- Specifying a wrong project identifier can lead to "not found" errors.
Error messages:
- 404 Not Found: The identity ID does not exist in the specified project. Verify the ID and project.
- 401 Unauthorized: Authentication failed. Check your API key credential.
- 400 Bad Request: Missing required parameters or malformed request. Ensure all required fields are provided.
To resolve these issues, verify the input parameters, ensure correct project and identity IDs, and confirm that the API key credential has appropriate permissions.
Links and References
- GateKit API Documentation (for detailed API endpoints and parameters)
- n8n HTTP Request Node Documentation (for understanding how API calls are made)