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 integrates with the X (Twitter) API v2 to perform various Twitter-related operations within n8n workflows. Specifically, for the Compliance resource and the Get Batch Job Status operation, it allows users to check the status of a previously created batch compliance job by providing its Job ID.

This is useful in scenarios where you have submitted a batch job to Twitter's compliance endpoints (e.g., for user or tweet data compliance) and want to programmatically monitor the progress or completion status of that job within your automation workflows.

Practical example:
You submit a batch job to retrieve compliance information about a set of tweets or users, then use this node operation to periodically check the job status until it completes, triggering subsequent workflow steps based on the result.

Properties

Name Meaning
Job ID The unique identifier of the batch compliance job whose status you want to check. This is required to query the job status.

Output

The node outputs JSON data representing the current status and details of the specified batch compliance job as returned by the Twitter API via the integrated service. The exact structure depends on Twitter's response but typically includes fields such as job state, creation time, completion time, and any errors or results associated with the job.

No binary data output is produced by this operation.

Dependencies

  • Requires an active subscription and valid API key credential for the external "N8N Tools API" service, which acts as a proxy or enhancer for Twitter API calls.
  • Requires proper Twitter API credentials configured in n8n to authorize requests.
  • The node internally validates the API key against the N8N Tools API before making Twitter API calls.
  • No additional environment variables are explicitly required beyond these credentials.

Troubleshooting

  • Invalid subscription or API key error:
    If the node throws an error indicating invalid subscription or API key, verify that your API key credential for the N8N Tools API is correct and active.

  • Job ID not found or invalid:
    Ensure the Job ID provided corresponds to an existing batch job. Mistyping or using an expired/incorrect Job ID will cause errors or empty responses.

  • Network or API errors:
    Temporary network issues or Twitter API rate limits may cause failures. Implement retry logic or error handling in your workflow.

  • Continue On Fail behavior:
    If enabled, the node will continue processing other items even if one fails, returning error details in the output.

Links and References

Discussion