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 manage direct message conversations, specifically allowing you to remove participants from a direct message conversation. It is useful in scenarios where you need to programmatically manage group conversations by removing one or more users from an ongoing direct message thread.
Practical examples include:
- Moderating group chats by removing inactive or unwanted participants.
- Automating cleanup of group conversations based on business rules.
- Managing membership dynamically in customer support or community engagement workflows.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The unique identifier of the direct message conversation from which participants will be removed. |
| Participant IDs | Comma-separated list of user IDs representing the participants to remove from the conversation. |
Output
The node outputs JSON data representing the result of the remove participants operation for each input item processed. The structure typically includes details about the updated conversation or confirmation of participant removal as returned by the Twitter API.
If multiple items are processed, the output is an array of such JSON objects, each corresponding to an input item.
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 that acts as a proxy or enhancer for Twitter API calls.
- Requires OAuth2 authentication credentials for Twitter API access.
- The node internally uses a helper class to interact with Twitter API v2 endpoints.
- Proper configuration of these credentials within n8n is necessary before use.
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 active.
- Permission Errors: Removing participants requires appropriate permissions on the Twitter account and conversation. Ensure the authenticated user has rights to modify the conversation.
- Malformed Participant IDs: Provide participant IDs as a comma-separated string without extra spaces or invalid characters.
- Conversation Not Found: Verify the conversation ID is correct and accessible by the authenticated user.
- API Rate Limits: Twitter API enforces rate limits; excessive requests may cause temporary failures.
- Continue On Fail: If enabled, errors for individual items will be captured in the output instead of stopping execution.
Links and References
- Twitter API v2 Documentation - Direct Messages
- n8n Documentation - Creating Custom Nodes
- X (Twitter) Developer Platform
This summary is based solely on static analysis of the provided source code and property definitions.