Actions74
- Lists Actions
- Tweets Actions
- Users Actions
- Timelines Actions
- Media Actions
- Spaces Actions
- Direct Messages Actions
- Analytics Actions
- Compliance Actions
Overview
This node provides enhanced integration with the X (formerly Twitter) API v2, enabling users to perform a wide range of operations related to tweets, users, timelines, media, spaces, lists, direct messages, analytics, and compliance. Specifically, for the Analytics resource with the Get Competitive Analysis operation, the node fetches competitive analysis data comparing multiple user accounts over a specified time period.
Typical use cases include marketing teams or social media analysts who want to compare the performance metrics of different Twitter users (e.g., competitors or influencers) to gain insights into engagement, reach, and other analytics over customizable periods such as 1 day, 7 days, 30 days, or 90 days.
Example: A social media manager can input several competitor user IDs and retrieve comparative analytics to inform strategy decisions.
Properties
| Name | Meaning |
|---|---|
| User IDs for Comparison | Comma-separated list of Twitter User IDs to compare in the competitive analysis report. |
| Period | Time period for the analysis. Options: "1 Day", "7 Days", "30 Days", "90 Days". |
Output
The node outputs JSON data containing the competitive analysis results for the specified user IDs over the selected period. The structure typically includes comparative metrics such as engagement rates, follower growth, tweet activity, and other relevant analytics aggregated per user.
If multiple items are processed, the output is an array of objects each corresponding to one input item, preserving the association between input and output.
No binary data output is produced by this operation.
Dependencies
- Requires an active subscription and valid API key credential for the external "N8N Tools API" service.
- The node internally uses a helper class that wraps calls to the Twitter API v2 endpoints.
- Proper OAuth2 or API key credentials for Twitter API access must be configured in n8n.
- The node performs a validation request to the external API before executing the main operation.
Troubleshooting
- Invalid Subscription or API Key: If the node throws an error indicating invalid subscription or API key, verify that the API key credential is correctly set up and has the necessary permissions.
- API Rate Limits: Twitter API enforces rate limits; excessive requests may result in errors or throttling. Consider adding delays or reducing batch sizes.
- Malformed User IDs: Ensure that the "User IDs for Comparison" property contains valid Twitter user IDs separated by commas without extra spaces.
- Network Issues: Connectivity problems with the external API or Twitter API will cause failures; check network status and proxy settings if applicable.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details per failed item.
Links and References
- Twitter API v2 Documentation
- N8N Official Documentation
- N8N Tools API - External Service (for subscription and API key management)