Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
The "Unreact" operation in the Messages resource allows users to remove a previously added reaction (emoji) from a specific message on a given messaging platform. This is useful in scenarios where a user or system wants to retract an emoji reaction, for example, if a reaction was added by mistake or needs to be updated.
Practical examples include:
- Removing a thumbs-up emoji reaction from a message in a team chat after a decision has changed.
- Retracting a heart emoji reaction from a social media post integrated via the messaging gateway.
- Managing reactions programmatically in automated workflows that track message sentiment or engagement.
Properties
| Name | Meaning |
|---|---|
Platform configuration ID (platformId) |
The identifier of the messaging platform configuration where the message exists. |
Message ID to unreact from (messageId) |
The unique identifier of the message from which the reaction should be removed. |
Emoji to remove (emoji) |
The emoji character representing the reaction to remove (e.g., "👍", "❤️"). |
Project (project) |
The project identifier within which this operation is performed (default is "default"). |
Output
The output JSON contains the response from the API endpoint that processes the removal of the reaction. Typically, this will confirm whether the unreact operation was successful and may include metadata about the message or the updated reactions state.
If the node supports binary data output, it is not indicated here; thus, the output is expected to be purely JSON-based.
Dependencies
- Requires an active API key credential configured with access to the messaging gateway API.
- The node sends a POST request to the
/api/v1/projects/{project}/messages/unreactendpoint with query parameters specifying the platform ID, message ID, and emoji. - The
projectparameter must correspond to a valid project in the messaging gateway system. - Proper permissions are required to modify message reactions on the specified platform.
Troubleshooting
Common issues:
- Invalid or missing
platformId,messageId, oremojiparameters will cause the API call to fail. - Insufficient permissions or invalid API credentials can result in authorization errors.
- Attempting to unreact an emoji that was not previously added may return an error or no effect.
- Network connectivity issues can prevent the request from reaching the API.
- Invalid or missing
Error messages and resolutions:
- "Unauthorized" or "Forbidden": Check API key validity and permissions.
- "Message not found": Verify the
messageIdis correct and exists on the specified platform. - "Invalid emoji" or "Reaction not found": Confirm the emoji string matches exactly the one used in the reaction.
- "Project not found": Ensure the
projectparameter corresponds to an existing project.
Links and References
- Messaging Gateway API Documentation (generic reference, replace with actual URL)
- Emoji standards and usage: https://unicode.org/emoji/
- n8n documentation on HTTP Request nodes and API integrations: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/