Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
This node interacts with the "Identities" resource of the GateKit API, specifically focusing on the "Messages" operation. It retrieves all messages associated with a particular identity across all linked platform accounts within a specified project. This is useful for scenarios where you want to aggregate or analyze communication history related to a user identity that may span multiple messaging platforms.
Practical examples include:
- Fetching all messages sent and received by a customer identified by their unique identity ID.
- Auditing message history for a specific user across integrated platforms like Telegram, Discord, or WhatsApp.
- Building reports or dashboards that consolidate user interactions from various messaging channels.
Properties
| Name | Meaning |
|---|---|
| Identity ID | The unique identifier of the identity whose messages you want to retrieve. |
| Project | The project identifier within which the identity exists. Typically used to scope requests. |
| Id | An additional id parameter (appears redundant with Identity ID; likely the same value). |
Output
The node outputs JSON data containing the list of messages associated with the specified identity. Each message record typically includes details such as message content, timestamps, platform information, sender/receiver metadata, and possibly linked reactions or other metadata depending on the API response.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for GateKit API access.
- The node expects the GateKit API base URL and authentication credentials to be configured in n8n credentials.
- The project identifier must be valid and correspond to an existing project in GateKit.
- The identity ID must correspond to an existing identity within the specified project.
Troubleshooting
- Invalid Identity ID: If the provided identity ID does not exist, the API will likely return a 404 error. Verify the identity ID is correct.
- Unauthorized Access: Missing or invalid API credentials will cause authentication errors. Ensure the API key credential is properly configured.
- Project Not Found: If the project identifier is incorrect or the user lacks access, requests will fail. Confirm the project ID and permissions.
- Empty Results: If no messages are returned, verify that the identity has linked platform accounts with message history.
- Parameter Confusion: The presence of both "Identity ID" and "Id" properties might confuse users; ensure consistent use of the identity identifier.
Links and References
- GateKit API Documentation (general reference for API endpoints)
- GateKit Messaging Concepts: managing identities and messages across platforms
- n8n documentation on creating HTTP Request nodes and using credentials
This summary is based solely on static analysis of the node's bundled source code and property definitions without runtime execution.