Actions74
- Lists Actions
- Tweets Actions
- Users Actions
- Timelines Actions
- Media Actions
- Spaces Actions
- Direct Messages Actions
- Analytics Actions
- Compliance Actions
Overview
This node integrates with the X (Twitter) API v2 to perform various operations related to Direct Messages, specifically including adding participants to a direct message conversation. The "Add Participants" operation allows users to add one or more users to an existing direct message conversation by specifying the conversation ID and the user IDs of the participants to add.
This functionality is useful in scenarios where you want to programmatically manage group conversations on Twitter, such as automating the inclusion of team members into ongoing discussions or managing customer support chats.
Example use case: Automatically add new team members to a customer support group conversation when they join the support team.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The unique identifier of the direct message conversation to which participants will be added. |
| Participant IDs | Comma-separated list of user IDs representing the participants to add to the conversation. |
Output
The node outputs JSON data representing the response from the Twitter API after attempting to add participants. This typically includes details about the updated conversation or confirmation of the successful addition of participants.
If multiple input items are processed, the output is an array of JSON objects corresponding to each item.
No binary data output is involved in this operation.
Dependencies
- Requires an active subscription and valid API key for the external service referred to as "N8N Tools API" for validation.
- Requires OAuth2 credentials for authenticating with the Twitter API v2.
- The node uses the bundled Twitter API client internally to interact with Twitter endpoints.
Troubleshooting
- Invalid Subscription or API Key: If the node throws an error indicating invalid subscription or API key, verify that your API key credential is correct and has the necessary permissions.
- API Rate Limits: Twitter API enforces rate limits; exceeding these may cause errors. Implement retry logic or reduce request frequency if needed.
- Incorrect Conversation ID or Participant IDs: Ensure that the conversation ID exists and participant IDs are valid Twitter user IDs. Invalid IDs will cause the API call to fail.
- Permission Issues: The authenticated user must have permission to modify the specified conversation. Lack of permission will result in authorization errors.