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, allowing users to perform a wide range of operations on various Twitter resources such as Tweets, Users, Timelines, Media, Spaces, Lists, Bookmarks, Direct Messages, Analytics, and Compliance jobs. Specifically for the Lists resource, it supports operations including creating, retrieving, updating, deleting lists, managing list members, following/unfollowing lists, pinning/unpinning lists, and fetching tweets from lists.
The Delete List operation enables users to delete a specified Twitter List by its ID. This is useful in scenarios where you want to programmatically manage your Twitter Lists, such as cleaning up outdated or irrelevant lists automatically within workflows.
Practical Example
- Automatically delete a Twitter List when a project ends or a campaign finishes.
- Clean up test or temporary lists created during automated testing or data collection.
- Manage lists dynamically based on external triggers or conditions in your workflow.
Properties
| Name | Meaning |
|---|---|
| List ID | The unique identifier of the Twitter List to delete. |
Output
The node outputs JSON data representing the response from the Twitter API after attempting to delete the list. Typically, this will include confirmation of deletion or relevant status information returned by the API.
The output structure is an array of items, each containing a json field with the API response and metadata about the item processed.
No binary data output is involved in this operation.
Dependencies
- Requires an active subscription and valid API key for the external "N8N Tools API" service used for validation.
- Requires credentials for authenticating with the Twitter API (via OAuth2 or API keys).
- 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 is correct and has the necessary permissions.
- List Not Found or Unauthorized: Errors may occur if the provided List ID does not exist or the authenticated user lacks permission to delete the list. Ensure the List ID is correct and the credentials have appropriate access.
- Network or API Errors: General HTTP errors from the Twitter API or the N8N Tools API can cause failures. Check network connectivity and API rate limits.
- Continue On Fail Behavior: If enabled, the node will continue processing other items even if one fails, returning error details per item.
Links and References
- Twitter API v2 Documentation - Lists
- X (Twitter) API v2 Reference
- n8n Documentation (for general usage of this node)