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, enabling comprehensive interaction with various Twitter resources including Tweets, Users, Timelines, Media, Spaces, Lists, Bookmarks, Direct Messages, Analytics, and Compliance features. Specifically for the Lists resource and the Pin List operation, it allows users to pin a specified Twitter List to their profile.
Practical scenarios where this node is beneficial include automating social media management workflows such as:
- Pinning important or frequently referenced Twitter Lists automatically based on certain triggers.
- Managing Twitter Lists programmatically within larger automation pipelines.
- Integrating Twitter List management into customer engagement or marketing workflows.
For example, a user can automate pinning a curated list of industry experts to their profile whenever the list is updated or created.
Properties
| Name | Meaning |
|---|---|
| List ID | The unique identifier of the Twitter List to be pinned. |
Output
The node outputs JSON data representing the response from the Twitter API after attempting to pin the specified List. This typically includes confirmation details about the pinned List or any relevant metadata returned by the API.
If multiple items are processed, the output is an array of such JSON objects, each corresponding to one input item.
No binary data output is produced by this operation.
Dependencies
- Requires an active subscription and valid API key for the external "N8N Tools API" service used for validation.
- Requires OAuth2 or API key credentials configured in n8n to authenticate with the Twitter API.
- The node depends on the bundled
twitter-apihelper class for making Twitter API calls. - Proper configuration of credentials and workflow permissions is necessary to perform List pinning operations.
Troubleshooting
- Invalid Subscription or API Key: If the node throws an error indicating invalid subscription or API key, verify that your N8N Tools API credentials are correct and have the required access.
- Twitter API Errors: Errors from Twitter API (e.g., invalid List ID, insufficient permissions) will be surfaced. Ensure the List ID is correct and the authenticated user has permission to pin the List.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if some fail, returning error details per failed item.
- Rate Limits: Be aware of Twitter API rate limits which may cause temporary failures; implement appropriate retry or backoff strategies.