TwitterDynamicAuth icon

TwitterDynamicAuth

Consume Twitter API using dynamic auth
Join our community

Actions6

Overview

This node allows users to create tweets on Twitter using the Twitter API. It supports posting a status update with optional additional fields such as attachments (media), location coordinates, reply to an existing tweet, and marking the tweet as possibly sensitive. This node is useful for automating social media posts, managing Twitter content programmatically, or integrating Twitter posting into workflows.

Use Case Examples

  1. Posting a simple tweet with text content.
  2. Posting a tweet with attached images or media files.
  3. Replying to an existing tweet by specifying the tweet ID.
  4. Adding location data to a tweet to share the exact coordinates of the post.

Properties

Name Meaning
Text The main text content of the tweet to be posted. This is required and should be URL encoded if necessary.
Additional Fields Optional fields to customize the tweet, including attachments, display coordinates, reply tweet ID, location coordinates, and sensitivity flag.

Output

JSON

  • id - The unique identifier of the created tweet.
  • text - The text content of the created tweet.
  • media_ids - Comma-separated IDs of media attached to the tweet, if any.
  • in_reply_to_status_id - ID of the tweet this tweet is replying to, if specified.
  • lat - Latitude coordinate of the tweet location, if provided.
  • long - Longitude coordinate of the tweet location, if provided.
  • possibly_sensitive - Flag indicating if the tweet media is marked as sensitive.

Dependencies

  • Twitter API with OAuth1 authentication

Troubleshooting

  • Ensure the Twitter API credentials are correctly configured and have permissions to post tweets.
  • Check that the text content does not exceed Twitter's character limits after URL encoding.
  • Verify that any media attachments are correctly uploaded and referenced by their binary property names.
  • If using location data, ensure latitude and longitude are valid numeric values.
  • Handle API rate limits and errors gracefully; the node supports continuing on failure to avoid workflow interruption.

Links

Discussion