N8N Tools - X (Twitter) Enhanced icon

N8N Tools - X (Twitter) Enhanced

Comprehensive X (Twitter) API v2 integration for N8N workflows
Join our community

Actions74

Overview

This node provides an enhanced integration with the X (formerly Twitter) API v2, enabling a wide range of operations on various Twitter resources. Specifically for the Lists resource and the Unpin List operation, the node allows users to unpin a specified list from their profile.

Use cases include managing Twitter lists programmatically within workflows, such as organizing followed lists by pinning or unpinning them based on dynamic conditions or user interactions. For example, a social media manager could automate the process of unpinning outdated or less relevant lists from their profile when new lists are created or priorities change.

Properties

Name Meaning
List ID The unique identifier of the list to unpin

Output

The node outputs JSON data representing the response from the Twitter API after attempting to unpin the specified list. This typically includes confirmation of the unpin action or details about the list's updated state.

The output is structured as an array of items, each containing a json field with the API response and metadata about the input item processed. There is no binary data output for this operation.

Example output snippet:

{
  "json": {
    // Response data confirming unpinning of the list
  },
  "itemData": {
    "item": 0
  }
}

Dependencies

  • Requires an active subscription and valid API key for the external "N8N Tools API" service used for validation.
  • Requires OAuth2 or API credentials configured in n8n to authenticate with the Twitter API.
  • The node depends on the bundled Twitter API client library for making requests.

Troubleshooting

  • Invalid subscription or API key error: If you receive an error indicating invalid subscription or API key, verify that your API key credential is correct and has the necessary permissions.
  • API request failures: Network issues or incorrect List IDs can cause errors. Ensure the List ID provided exists and belongs to the authenticated user.
  • Continue on Fail: If enabled, the node will continue processing other items even if one fails, returning error details in the output.

Links and References

Discussion