Actions74
- Lists Actions
- Tweets Actions
- Users Actions
- Timelines Actions
- Media Actions
- Spaces Actions
- Direct Messages Actions
- Analytics Actions
- Compliance Actions
Overview
This node integrates with the X (Twitter) API v2 to perform various timeline-related operations. Specifically, for the Timelines - Get Liked Tweets operation, it retrieves tweets that a specified user has liked. This is useful for workflows that need to analyze or process content a user has engaged with positively.
Common scenarios include:
- Monitoring liked tweets of a user to gather insights or trigger actions based on their interests.
- Archiving or backing up liked tweets for personal or organizational use.
- Feeding liked tweet data into analytics or reporting tools.
Example: You want to automatically collect the latest 20 tweets liked by a particular user and then analyze their sentiment or share them in a newsletter.
Properties
| Name | Meaning |
|---|---|
| User ID | The user identifier or @username whose liked tweets you want to retrieve. |
| Max Results | Maximum number of liked tweets to return (1 to 100). |
| Pagination Token | Token used to paginate through results if there are more than one page. |
| Include Private Metrics | Whether to include private engagement metrics (requires elevated API access). |
| Custom Fields | Comma-separated list of additional custom fields to include in the response. |
| Custom Expansions | Comma-separated list of expansions to include additional related objects in the response. |
Output
The node outputs an array of JSON objects representing the liked tweets retrieved from the Twitter API. Each object contains detailed tweet data including text, author information, timestamps, and optionally expanded fields and metrics depending on the input parameters.
If private metrics are included, additional engagement statistics such as impression counts may be present.
No binary data output is produced by this operation.
Dependencies
- Requires a valid API key credential for the external "N8N Tools API" service to validate subscription and usage.
- Requires OAuth2 or API credentials configured for accessing the Twitter API v2.
- The node uses the bundled
twitter-apihelper class to interact with Twitter endpoints. - Network connectivity to Twitter API endpoints 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 your API key credential for the external validation service is correct and active.
- API rate limits: Twitter API enforces rate limits; exceeding these will cause errors. Consider handling pagination tokens properly and limiting max results.
- Missing or incorrect User ID: Ensure the User ID or username provided is valid and accessible by your credentials.
- Include Private Metrics requires elevated access: If you enable private metrics without proper API access level, the request may fail.
- Pagination token issues: Using an invalid or expired pagination token can result in empty or error responses.