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 comprehensive interaction with various Twitter resources including Tweets, Users, Timelines, Media, Spaces, Lists, Bookmarks, Direct Messages, Analytics, and Compliance features. Specifically for the Spaces resource, the node supports operations such as creating, retrieving, updating, starting, ending, deleting spaces, and fetching related data like buyers or tweets within a space.
The End Space operation allows users to programmatically end a live Space on Twitter. This is useful in scenarios where you want to automate the management of live audio conversations, for example:
- Automatically ending a Space after a scheduled time.
- Integrating Space lifecycle control into broader social media workflows.
- Managing multiple Spaces dynamically without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Space ID | The unique identifier of the Space to be ended. |
Output
The node outputs JSON data representing the response from the Twitter API after attempting to end the specified Space. This typically includes details about the Space's updated status or confirmation that the Space has been ended successfully.
If multiple input items are processed, the output will be an array of JSON objects corresponding to each item’s result.
No binary data output is involved in this operation.
Dependencies
- Requires an active subscription and valid API key for the external "N8N Tools API" service used for validation.
- Requires credentials for authenticating with the Twitter API (via OAuth2 or API keys).
- The node uses the bundled
TwitterApihelper class to interact with Twitter endpoints. - Proper configuration of these credentials in n8n is necessary before use.
Troubleshooting
- Invalid subscription or API key error: If the node throws an error indicating invalid subscription or API key, verify that your API key credential for the external validation service is correct and active.
- Twitter API errors: Errors returned by Twitter (e.g., invalid Space ID, permission issues) will be surfaced. Ensure the Space ID is correct and that the authenticated user has permissions to manage 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, collecting errors in the output.