Actions74
- Lists Actions
- Tweets Actions
- Users Actions
- Timelines Actions
- Media Actions
- Spaces Actions
- Direct Messages Actions
- Analytics Actions
- Compliance Actions
Overview
The node provides an enhanced integration with the X (formerly Twitter) API v2, enabling comprehensive interaction with various Twitter resources. Specifically for the Compliance resource and the Full Archive Search operation, it allows users to perform a full archive search of tweets based on a query string. This is useful for retrieving historical tweet data beyond the standard recent search limits, which can be essential for compliance monitoring, research, or analytics.
Typical use cases include:
- Compliance teams searching the entire Twitter archive for specific keywords or phrases.
- Researchers analyzing historical tweet data for trends or events.
- Legal or regulatory audits requiring access to older tweets matching certain criteria.
Example: Searching the full Twitter archive for tweets containing "data privacy" to monitor compliance-related discussions over time.
Properties
| Name | Meaning |
|---|---|
| Environment | Premium environment label required to specify the Twitter premium environment to use. |
Output
The node outputs JSON data representing the results of the full archive search query. The structure typically includes tweet objects matching the search criteria, along with any metadata returned by the Twitter API such as pagination tokens or result counts.
If multiple input items are processed, the output is an array where each element corresponds to the search results for that item.
No binary data output is indicated for this operation.
Dependencies
- Requires an active subscription to a premium Twitter environment that supports full archive search.
- Needs an API key credential for the external service called "N8N Tools API" to validate subscription and usage.
- Uses the Twitter API v2 via a helper class internally.
- Proper configuration of credentials in n8n for both the Twitter API and the N8N Tools API is necessary.
Troubleshooting
- Invalid subscription or API key error: If the node throws an error about invalid subscription or API key, verify that the provided API key is correct and that the Twitter premium environment subscription is active.
- Missing or incorrect environment label: Ensure the "Environment" property is set correctly to the premium environment label assigned by Twitter.
- API rate limits: Full archive searches may be subject to rate limits; if requests fail due to rate limiting, consider adding delays or reducing request frequency.
- Network or connectivity issues: Errors during HTTP requests to the validation endpoint or Twitter API may indicate network problems; check connectivity and proxy settings if applicable.