N8N Tools - YouTube Enhanced
Actions83
- Videos Actions
- Channels Actions
- Playlists Actions
- Search Actions
- Analytics Actions
- Get Channel Analytics
- Get Video Analytics
- Get Playlist Analytics
- Get Content Owner Analytics
- Get Audience Retention
- Get Demographics
- Get Geographic Data
- Get Device Data
- Get Traffic Source Data
- Get Revenue Data
- Get Ad Performance Data
- Get Subscriber Analytics
- Get Playback Location Data
- Get Video Performance Data
- Get Playlist Performance Data
- Get Annotation Performance Data
- Get Card Performance Data
- Get Sharing Service Data
- Get Live Streaming Data
- Get Content Type Data
- Get Time Based Data
- Comments Actions
- Subscriptions Actions
- Live Streaming Actions
- Video Upload Actions
- Community Posts Actions
- Thumbnails Actions
- Captions Actions
- Channel Memberships Actions
- Super Chat & Thanks Actions
Overview
This node operation deletes a specific YouTube Community Post identified by its Post ID. It is useful for content creators or channel managers who want to programmatically remove outdated, inappropriate, or unwanted community posts from their YouTube channel. For example, if a user wants to automate the cleanup of community posts based on certain criteria or schedule deletions, this operation can be integrated into an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| Post ID | The unique identifier of the community post to delete. |
Output
The output JSON contains the response from the API after attempting to delete the specified community post. Typically, this will include confirmation of deletion or any error messages returned by the service. The exact structure depends on the underlying API response but generally indicates success or failure of the deletion request.
No binary data output is involved in this operation.
Dependencies
- Requires an active subscription and valid API key credential for the external "N8N Tools" API service.
- Requires OAuth2 credentials for YouTube API access.
- The node uses the YouTube Community Posts API via the bundled helper classes.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Invalid API Key or Subscription: If the node throws an error about invalid subscription or API key, verify that the API key credential is correctly configured and active.
- Post Not Found or Unauthorized: Errors may occur if the provided Post ID does not exist or the authenticated user lacks permission to delete the post. Confirm the Post ID is correct and the credentials have sufficient permissions.
- Network or API Errors: Temporary network issues or API rate limits might cause failures. Retrying after some time or checking API quota usage can help.
- Continue On Fail Behavior: If enabled, the node will continue processing other items even if one deletion fails, returning error details per item.