Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
This node provides access to the "Identities" resource of a universal messaging gateway platform, specifically supporting the "Get" operation. It allows you to retrieve detailed information about a specific identity within a project by its unique Identity ID. This is useful in scenarios where you need to fetch user or identity details for further processing, auditing, or integration with other systems.
For example, you might use this node to:
- Retrieve an identity's metadata and aliases before sending targeted messages.
- Fetch identity details to synchronize with an external CRM or user database.
- Audit identity information as part of compliance or reporting workflows.
Properties
| Name | Meaning |
|---|---|
| Identity ID | The unique identifier of the identity to retrieve. |
| Project | The project identifier under which the identity exists; used to scope the request. |
| Id | Alias for the Identity ID parameter (also required); represents the identity's ID. |
Note: The properties "Identity ID" and "Id" both represent the identity's unique ID and are required. "Project" specifies the project context.
Output
The output JSON contains the full details of the requested identity as returned by the API. This typically includes fields such as the identity's display name, email, metadata, platform aliases, and other relevant attributes associated with that identity.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the messaging gateway API.
- The node uses the base URL from the provided credentials to make HTTP GET requests.
- The "project" property must be set correctly to target the appropriate project context in the API.
Troubleshooting
- Missing or invalid Identity ID: Ensure the "Identity ID" or "Id" property is provided and correctly matches an existing identity in the specified project.
- Invalid project identifier: Verify that the "Project" property corresponds to a valid project accessible with your API credentials.
- Authentication errors: Confirm that the API key credential is valid and has permissions to read identities.
- Not found errors: If the identity does not exist, the API will likely return a 404 error. Double-check the ID and project.
- Network or connectivity issues: Ensure that the n8n instance can reach the API endpoint defined in the credentials.
Links and References
- MsgCore API Documentation (generic reference, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding how API calls are made
- General info on managing identities in messaging platforms (varies by provider)