Actions74
- Lists Actions
- Tweets Actions
- Users Actions
- Timelines Actions
- Media Actions
- Spaces Actions
- Direct Messages Actions
- Analytics Actions
- Compliance Actions
Overview
This node enables interaction with the X (formerly Twitter) API v2, providing enhanced capabilities for managing various Twitter resources within n8n workflows. Specifically, the "Direct Messages" resource with the "React to Message" operation allows users to add an emoji reaction to a specific direct message by its ID.
Use cases include:
- Automatically reacting to incoming direct messages with predefined emojis as part of customer support automation.
- Adding reactions to messages in group conversations to acknowledge receipt or express sentiment without sending a new message.
- Integrating Twitter direct message reactions into broader social media management workflows.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique identifier of the direct message to which you want to add a reaction. |
| Emoji | The emoji character or shortcode to react with on the specified message. |
Output
The node outputs JSON data representing the result of the reaction action performed on the direct message. This typically includes confirmation details from the Twitter API about the reaction added.
No binary data output is involved in this operation.
Dependencies
- Requires an active subscription and valid API key for the external service referred to as "N8N Tools API" for validation.
- Requires authentication credentials for the Twitter API (OAuth2 or API key-based).
- The node uses an internal helper class to interact with the Twitter API v2 endpoints.
Troubleshooting
- Invalid Subscription or API Key: If the node throws an error indicating invalid subscription or API key, verify that your API key credential for the external validation service is correct and active.
- Message Not Found or Invalid Message ID: Ensure the provided Message ID exists and is accessible by the authenticated user.
- Emoji Format Issues: The emoji must be a valid Unicode emoji or supported shortcode; otherwise, the Twitter API may reject the request.
- Permission Errors: The authenticated Twitter account must have permission to react to the specified message; otherwise, authorization errors may occur.
- Network or API Rate Limits: Network issues or hitting Twitter API rate limits can cause failures; consider adding retry logic or handling rate limit responses gracefully.