Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
The node provides integration with a universal messaging gateway called GateKit, enabling interaction with multiple messaging platforms through a single interface. Specifically, the "Messages" resource with the "Get" operation allows users to retrieve detailed information about a specific message by its unique ID within a given project.
This node is beneficial in scenarios where you need to fetch and analyze individual messages sent or received across various platforms managed under a project. For example, it can be used to audit message content, check delivery details, or debug issues related to a particular message.
Practical examples:
- Retrieve the full details of a customer support message to review conversation history.
- Fetch a message by ID to verify its status or metadata before triggering further automation.
- Use the message data for reporting or analytics purposes.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique identifier of the message to retrieve. |
| Project | The identifier of the project under which the message exists; defaults to "default". |
Output
The output contains a JSON object representing the detailed data of the requested message. This typically includes all message attributes as stored in the GateKit system, such as content, sender, timestamps, platform-specific metadata, and possibly reactions or delivery status.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the GateKit API.
- Needs configuration of the base URL for the GateKit API endpoint via credentials.
- The node makes HTTP GET requests to the GateKit API to fetch message data.
Troubleshooting
- Common issue: Providing an incorrect or non-existent Message ID will likely result in an error or empty response. Ensure the Message ID is valid and belongs to the specified project.
- Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Verify that the API key is correctly configured.
- Project not found: Using an incorrect project identifier may cause the API to return errors. Confirm the project name or ID is correct.
- Network issues: Connectivity problems to the GateKit API endpoint will prevent successful retrieval. Check network access and API URL configuration.
Links and References
- GateKit API Documentation (hypothetical link)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics