Actions74
- Lists Actions
- Tweets Actions
- Users Actions
- Timelines Actions
- Media Actions
- Spaces Actions
- Direct Messages Actions
- Analytics Actions
- Compliance Actions
Overview
This node provides enhanced integration with the X (formerly Twitter) API v2, enabling various operations on Twitter resources within n8n workflows. Specifically for the Spaces resource and the Delete Space operation, it allows users to delete a Twitter Space by specifying its unique Space ID.
Use cases include managing live audio conversations on Twitter by programmatically deleting Spaces that are no longer needed or were created in error. For example, an event organizer could automate the cleanup of Spaces after events conclude.
Properties
| Name | Meaning |
|---|---|
| Space ID | The unique identifier of the Twitter Space to delete |
Output
The node outputs JSON data representing the response from the Twitter API after attempting to delete the specified Space. This typically includes confirmation of deletion or details about the deleted Space.
The output is structured as an array of items, each containing a json field with the API response and metadata about the item processed.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for the "N8N Tools API" service to validate subscription and access.
- Requires OAuth2 or API credentials for authenticating with the Twitter API.
- The node uses an internal helper class to interact with Twitter's API endpoints.
- Proper configuration of these credentials in n8n is necessary for successful execution.
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.
- Twitter API errors: Errors returned from Twitter (e.g., invalid Space ID, insufficient permissions) will be surfaced. Ensure the Space ID is valid and the authenticated user has rights to delete the Space.
- Network or connectivity issues: Failures in HTTP requests may occur due to network problems; retry or check connectivity.
- Continue on Fail: If enabled, the node will continue processing other items even if one fails, returning error details in the output.