Actions74
- Lists Actions
- Tweets Actions
- Users Actions
- Timelines Actions
- Media Actions
- Spaces Actions
- Direct Messages Actions
- Analytics Actions
- Compliance Actions
Overview
This node provides an enhanced integration with the X (formerly Twitter) API v2, enabling comprehensive interaction with various Twitter resources including tweets, users, timelines, media, spaces, lists, bookmarks, direct messages, analytics, and compliance features.
Specifically for the Compliance resource with the Thirty Day Search operation, the node allows users to perform searches on Twitter data from the past 30 days within a premium environment. This is useful for compliance monitoring, content auditing, or regulatory reporting where recent tweet data needs to be searched and analyzed.
Practical examples include:
- Searching for tweets containing specific keywords or hashtags posted in the last 30 days.
- Monitoring recent user activity for compliance purposes.
- Auditing recent tweet content for policy enforcement.
Properties
| Name | Meaning |
|---|---|
| Environment | Premium environment label required to access the thirty day search feature. |
Output
The node outputs JSON data representing the results of the thirty day search query. The structure depends on the Twitter API response but generally includes tweet objects matching the search criteria along with any requested expansions or fields.
If multiple input items are processed, the output is an array of JSON objects corresponding to each item’s result.
No binary data output is produced by this operation.
Dependencies
- Requires a valid API key credential for the external "N8N Tools API" service to validate subscription and access.
- Requires Twitter API credentials with appropriate permissions to perform compliance-related searches.
- The "Environment" property must be set to a valid premium environment label to use the thirty day search endpoint.
Troubleshooting
- Invalid subscription or API key error: If the node throws an error indicating invalid subscription or API key, verify that the API key credential is correct and active.
- Missing or incorrect environment label: Ensure the "Environment" property is correctly set to a premium environment label provided by the service.
- API rate limits: Twitter API may enforce rate limits; if requests fail due to rate limiting, consider adding delays or reducing request frequency.
- Network or connectivity issues: Verify network access to both the N8N Tools API and Twitter API endpoints.