Actions74
- Lists Actions
- Tweets Actions
- Users Actions
- Timelines Actions
- Media Actions
- Spaces Actions
- Direct Messages Actions
- Analytics Actions
- Compliance Actions
Overview
The node provides integration with the X (Twitter) API v2, enabling various operations across multiple Twitter resources. Specifically for the Compliance resource and the Create Batch Job operation, it allows users to create batch compliance jobs on Twitter. This is useful for submitting large sets of user or tweet IDs to Twitter for compliance-related processing, such as checking account or content status in bulk.
Typical use cases include:
- Submitting a batch of user IDs or tweet IDs to Twitter for compliance checks.
- Automating compliance workflows where large datasets need to be processed by Twitter's compliance endpoints.
- Integrating Twitter compliance job creation into broader automation pipelines within n8n.
Example: A user wants to submit a batch job to check the compliance status of multiple tweets at once. They select the Compliance resource, choose the Create Batch Job operation, specify the job type (e.g., "tweets"), and provide a list of tweet IDs.
Properties
| Name | Meaning |
|---|---|
| Job Type | Type of compliance or batch job to create. Options: Tweets, Users, User Lookup, Tweet Lookup, Followers, Following |
Output
The node outputs JSON data representing the response from the Twitter API after creating the batch job. The output includes details about the created batch job, such as its ID and status information returned by Twitter.
The output structure is an array of items, each containing a json field with the API response data related to the batch job creation.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for the external "N8N Tools API" service used for validation.
- Requires valid Twitter API credentials (OAuth2 or API key) configured in n8n to authenticate requests to Twitter.
- The node uses an internal helper class to interact with Twitter's API v2 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 for the external validation service is correct and active.
- API request failures: Errors from Twitter API calls may occur due to invalid parameters, rate limits, or insufficient permissions. Check the job type and data provided are valid and conform to Twitter's API requirements.
- Empty or malformed user ID list: When providing the list of IDs for the batch job, ensure they are comma-separated and trimmed properly. Malformed input can cause errors.
- Continue on Fail: The node supports continuing execution on failure for individual items; enable this option if you want partial success without stopping the workflow.