Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
The "Get Message" operation of the MsgCore node allows you to retrieve detailed information about a specific message by its unique identifier within a given project. This is useful when you want to fetch the content, metadata, status, or other details of a particular message that was sent or received through the messaging gateway.
Common scenarios include:
- Auditing or reviewing a specific message's details.
- Fetching message data for further processing or logging.
- Integrating with other systems that require message content retrieval by ID.
For example, you might use this operation to get the full details of a customer support message sent via Telegram or Discord to analyze the conversation or check delivery status.
Properties
| Name | Meaning |
|---|---|
| Project | The identifier of the project in which the message exists. |
| Message ID | The unique identifier of the message to retrieve. |
Output
The output will contain a JSON object representing the detailed information of the requested message. This typically includes fields such as message content, sender and recipient details, timestamps, status, platform-specific data, and any associated metadata.
If the message contains binary data (e.g., attachments), it would be included in the output accordingly, but this operation primarily returns structured JSON data describing the message.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the MsgCore API.
- The node makes HTTP GET requests to the MsgCore API endpoint corresponding to the specified project and message ID.
- The user must have appropriate permissions to access the message data within the specified project.
Troubleshooting
- Missing or invalid Message ID: Ensure the Message ID property is provided and correctly references an existing message.
- Invalid Project Identifier: Verify that the project name or ID is correct and accessible with your credentials.
- Authentication errors: Confirm that the API key credential is valid and has sufficient permissions.
- Message not found: If the message ID does not exist in the project, the API may return a 404 error. Double-check the ID.
- Network issues: Check connectivity to the MsgCore API endpoint and ensure no firewall or proxy blocks the request.
Links and References
- MsgCore API Documentation (replace with actual URL if available)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls.