GateKit icon

GateKit

Universal messaging gateway - send messages across multiple platforms

Actions51

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 it was added by mistake or if the sentiment has changed.

Practical examples:

  • Removing a "thumbs up" emoji reaction from a message in a team chat after reconsideration.
  • Automatically clearing reactions as part of a moderation workflow.
  • Managing message reactions programmatically across multiple platforms via a unified API.

Properties

Name Meaning
Platform configuration ID The identifier of the messaging platform configuration where the message exists.
Message ID to unreact from The unique identifier of the message from which the reaction should be removed.
Emoji to remove (e.g., "👍", "❤️") The specific emoji character representing the reaction to be removed from the message.
Project The project identifier within which this operation is performed (usually a workspace or environment context).

Output

The output will contain the JSON response from the API indicating the result of the unreact operation. Typically, this includes confirmation that the reaction was successfully removed or details about any errors encountered.

If the node supports binary data output, it is not applicable here since this operation deals with message metadata (reactions) rather than media content.

Dependencies

  • Requires an active API key credential configured in n8n to authenticate requests against the GateKit messaging gateway API.
  • The node sends a POST request to the endpoint /api/v1/projects/{project}/messages/unreact with query parameters specifying the platform ID, message ID, and emoji.
  • The project parameter must correspond to a valid project configured in the GateKit system.
  • The platform configuration ID must refer to a valid platform integration within the project.

Troubleshooting

  • Common issues:

    • Invalid or missing platform ID, message ID, or emoji parameters will cause the API to reject the request.
    • Attempting to unreact with an emoji that was not previously added may result in no change or an error.
    • Insufficient permissions or invalid API credentials can cause authentication failures.
    • Network connectivity issues or incorrect base URL configuration can prevent successful API calls.

  • Error messages:

    • "Unauthorized" or "Authentication failed": Check that the API key credential is correctly set up and has necessary permissions.
    • "Message not found": Verify the message ID and platform ID are correct and exist in the specified project.
    • "Invalid emoji" or "Reaction not found": Confirm the emoji string matches exactly the one used in the reaction.
    • "Project not found": Ensure the project identifier is valid and accessible.

Resolving these typically involves verifying input parameters, checking API credentials, and ensuring the target message and platform exist.

Links and References

Discussion