N8N Tools - X (Twitter) Enhanced icon

N8N Tools - X (Twitter) Enhanced

Comprehensive X (Twitter) API v2 integration for N8N workflows

Overview

This node integrates with the X (formerly Twitter) API v2 to perform various operations related to direct messages, including creating group conversations. Specifically, the "Create Group Conversation" operation allows users to start a new group direct message conversation by specifying multiple participant user IDs.

This functionality is useful for automating communication workflows on X, such as initiating group chats among team members, customers, or community participants directly from an n8n workflow. For example, a marketing automation workflow could create a group conversation with selected users to coordinate campaign discussions.

Properties

Name Meaning
Participant IDs Comma-separated User IDs to include in the group conversation

Output

The node outputs JSON data representing the response from the X API after creating the group conversation. This typically includes details about the newly created conversation such as its ID and metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for accessing the N8N Tools API service.
  • Requires OAuth2 or API credentials for authenticating with the X (Twitter) API v2.
  • The node internally validates the subscription and API key against the N8N Tools API before making requests.
  • 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 the provided API key credential is correct and active.
  • Malformed participant IDs: Ensure the "Participant IDs" input is a properly formatted comma-separated list of valid user IDs. Invalid or empty IDs may cause API errors.
  • API rate limits: The X API enforces rate limits; excessive requests may result in throttling errors. Implement retry logic or reduce request frequency if needed.
  • Network or connectivity issues: Check network access and proxy settings if HTTP requests fail.

Links and References

Discussion