Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
This node interacts with a universal messaging gateway API to retrieve all messages associated with a specific identity across all linked platform accounts. It is useful for scenarios where you want to aggregate or analyze communication history of a user identified by their unique identity ID within a project. For example, you could use this node to fetch all chat messages sent and received by a customer across multiple platforms (like Telegram, Discord, WhatsApp) linked to their identity in your system.
Properties
| Name | Meaning |
|---|---|
| Identity ID | The unique identifier of the identity whose messages you want to retrieve. |
| Project | The project identifier under which the identity exists; used to scope the API request. |
| Id | An additional id parameter (likely same as Identity ID), required for the operation routing. |
Output
The output contains a JSON field with the list of messages associated with the specified identity. Each message represents a communication instance from any linked platform account under that identity. The structure typically includes message metadata such as timestamps, content, sender/receiver info, platform details, and possibly reactions or raw platform data if requested.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authentication to the messaging gateway API.
- The node expects the base URL of the API to be configured in the credentials.
- The project identifier must correspond to a valid project in the messaging gateway system.
Troubleshooting
- Invalid Identity ID: If the provided identity ID does not exist or is incorrect, the API will likely return a 404 error. Verify the identity ID is correct.
- Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Ensure the API key is correctly set up in n8n credentials.
- Project Not Found: Using an invalid or misspelled project identifier may result in errors. Confirm the project name matches exactly.
- Empty Results: If no messages are returned, verify that the identity has linked platform accounts and messages exist.
- API Rate Limits: Excessive requests might trigger rate limiting; consider adding delays or handling retries.
Links and References
- MsgCore API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation for understanding how API calls are made.
- Messaging Gateway Platform User Guide for managing identities and messages.