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 such as Tweets, Users, Timelines, Media, Spaces, Lists, Bookmarks, Direct Messages, Analytics, and Compliance features. Specifically for the "Lists" resource and the "Get List" operation, it retrieves detailed information about a specified Twitter List by its ID.
Common scenarios where this node is beneficial include:
- Fetching metadata and details of a specific Twitter List to analyze or display in workflows.
- Automating social media management tasks that require list data retrieval.
- Integrating Twitter List information into broader data processing or reporting pipelines.
Practical example:
- A marketing team uses this node to automatically fetch and update details of curated Twitter Lists they manage, integrating the data into dashboards or CRM systems.
Properties
| Name | Meaning |
|---|---|
| List ID | The unique identifier of the Twitter List to retrieve. |
Output
The node outputs JSON data representing the retrieved Twitter List object. This includes all available fields and expansions supported by the Twitter API for Lists, such as the list's name, description, privacy status, member count, and other metadata.
The output structure corresponds directly to the Twitter API response for a List object, allowing downstream nodes to access any part of the list's data.
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, which validates usage before forwarding requests to Twitter.
- Requires OAuth2 or API credentials configured for accessing the Twitter API v2.
- The node depends on the bundled
twitter-apihelper class for making authenticated calls to Twitter endpoints.
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 correctly set up and has an active subscription with the external validation service.
- Twitter API errors: Errors from Twitter (e.g., invalid List ID, permission issues) will be surfaced. Ensure the List ID is correct and the authenticated user has access rights.
- Network or connectivity issues: Failures in HTTP requests may occur due to network problems; check connectivity and proxy settings if applicable.
- Unsupported file upload URLs: For media operations (not relevant here), base64 encoded data must be used instead of URLs.
If the node is set to continue on failure, errors for individual items will be returned in the output array alongside successful results.