Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
This node provides an interface to manage identities within a messaging platform project. Specifically, the "Delete" operation under the "Identities" resource allows users to delete an identity and all its associated aliases from a specified project. This is useful for cleaning up or removing user identities that are no longer needed or valid.
Practical scenarios include:
- Removing a user identity when they leave a service or revoke permissions.
- Cleaning up test or temporary identities created during development.
- Managing data privacy by deleting personal information upon request.
Properties
| Name | Meaning |
|---|---|
| Identity ID to delete (id) | The unique identifier of the identity to be deleted. This is required to specify which identity to remove. |
| Project | The identifier of the project in which the identity exists. Defaults to "default". |
| Id | Another field representing the identity's ID parameter (appears redundant with "Identity ID to delete"). |
Note: The properties "Identity ID to delete" and "Id" both represent the identity's ID to delete; likely only one is used depending on context.
Output
The output JSON will contain the response from the API after attempting to delete the specified identity. Typically, this would be a confirmation of deletion or an error message if the deletion failed.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the messaging platform's API.
- The node sends HTTP DELETE requests to the endpoint
/api/v1/projects/{project}/identities/{id}where{project}and{id}are provided by the input parameters. - The base URL for the API is taken from the credentials configuration.
Troubleshooting
Common issues:
- Providing an invalid or non-existent identity ID will result in an error indicating the identity was not found.
- Insufficient permissions or missing API authentication token can cause authorization errors.
- Incorrect project identifier may lead to failure in locating the identity.
Error messages:
- 404 Not Found: The specified identity ID does not exist in the given project.
- 401 Unauthorized: Authentication failed due to missing or invalid API key.
- 400 Bad Request: Missing required parameters such as identity ID or project.
Resolution:
- Verify the identity ID and project values are correct.
- Ensure the API key credential is properly set up and has sufficient permissions.
- Check network connectivity and API endpoint availability.
Links and References
- MsgCore API Documentation (generic link, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding how API calls are made.
- General best practices for managing user identities and GDPR compliance.