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

The "Get Me" operation under the "Users" resource in this node retrieves detailed information about the authenticated Twitter user. This includes standard user profile data and optionally additional fields such as custom expansions and private metrics if enabled.

This operation is useful when you want to programmatically obtain your own Twitter account details within an n8n workflow, for example:

  • To verify the authenticated user's identity.
  • To fetch profile information for personalization or logging.
  • To gather metrics related to your own account for analytics or reporting.

Properties

Name Meaning
Include Private Metrics Boolean flag to include private metrics in the response (requires elevated access).
Custom Fields Comma-separated list of additional user fields to include in the response.
Custom Expansions Comma-separated list of expansions to include, allowing retrieval of related objects.

Output

The output JSON contains the user object representing the authenticated user with fields depending on the requested custom fields and expansions. It typically includes:

  • Basic profile information such as username, name, ID, description, etc.
  • Additional fields specified via "Custom Fields".
  • Related objects included via "Custom Expansions".
  • Optionally, private metrics if "Include Private Metrics" is enabled and permitted.

No binary data is produced by this operation.

Example output structure (simplified):

{
  "data": {
    "id": "123456789",
    "name": "Your Name",
    "username": "yourusername",
    "description": "Profile description",
    "...": "Other standard or custom fields"
  },
  "includes": {
    "...": "Expanded related objects if any"
  },
  "private_metrics": {
    "...": "Private metrics if included"
  }
}

Dependencies

  • Requires a valid API key credential for the external service called "N8N Tools API" to validate subscription and access.
  • Requires Twitter API credentials (OAuth2 or API key) configured in n8n to authenticate requests to Twitter's API v2.
  • The node uses an internal helper class to interact with Twitter API 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 correctly set up and active.
  • Permission errors when including private metrics: Including private metrics requires elevated access from Twitter. Ensure your Twitter app has the necessary permissions.
  • Malformed custom fields or expansions: Provide comma-separated strings without extra spaces or invalid field names to avoid API errors.
  • Network or rate limit issues: Twitter API enforces rate limits; handle errors accordingly and consider retry logic or reducing request frequency.

Links and References

Discussion