Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
The "React" operation of the Messages resource in this node allows users to add an emoji reaction to a specific message on a configured messaging platform. This is useful for automating or integrating reactions into workflows, such as acknowledging messages, expressing sentiment, or triggering further actions based on reactions.
Practical examples include:
- Automatically reacting with a thumbs-up emoji ("👍") to confirm receipt of a message.
- Adding heart ("❤️") or other emojis to highlight important messages.
- Integrating with chat platforms like Telegram, Discord, or WhatsApp to manage message reactions programmatically.
This operation simplifies interaction with multiple messaging platforms through a unified API.
Properties
| Name | Meaning |
|---|---|
Platform configuration ID (platformId) |
The identifier of the messaging platform configuration where the message exists. |
Message ID to react to (messageId) |
The unique identifier of the message to which the reaction will be added. |
Emoji to react with (emoji) |
The emoji character(s) used to react to the message (e.g., "👍", "❤️"). |
Project (project) |
The project identifier under which the operation is performed (default is "default"). |
Output
The output JSON contains the response from the API after adding the reaction to the specified message. It typically includes confirmation details about the reaction added, such as the emoji used and the message it was applied to.
No binary data output is involved in this operation.
Dependencies
- Requires an active API key credential configured in n8n to authenticate requests.
- Needs the GateKit API URL set in credentials to route requests properly.
- The target messaging platform must be configured and active within the specified project.
Troubleshooting
- Invalid Platform ID or Message ID: If the platform or message ID is incorrect or does not exist, the API will return an error. Verify IDs are correct and correspond to existing entities.
- Emoji Format Issues: Ensure the emoji string is valid and supported by the target platform. Some platforms may have restrictions on allowed emojis.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm that the API key credential is correctly set up.
- Permission Denied: The API user might lack permissions to react to messages in the specified project or platform. Check user roles and access rights.
- Network or API Endpoint Issues: Connectivity problems or incorrect API base URLs can cause request failures. Validate network access and credential configurations.
Links and References
- GateKit API Documentation (for detailed API endpoints and platform capabilities)
- Unicode Emoji List (to find valid emoji characters)