Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node allows you to delete a single message thread by specifying its unique identifier. It is useful in scenarios where you want to programmatically remove conversations or threads from a messaging system, such as cleaning up old or irrelevant discussions, managing user data, or automating moderation tasks.
For example, if you have an application that integrates with a messaging platform and you want to delete a specific conversation thread based on user input or automated rules, this node can perform that deletion efficiently.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the message thread to delete. This is a required string value representing the object id of the thread. |
Output
The output of this node will typically contain JSON data indicating the result of the delete operation. This may include confirmation of successful deletion or details about the deleted thread. Since the operation is a deletion, no binary data output is expected.
Dependencies
- Requires an API key credential for authentication to the external service providing the messaging functionality.
- The node uses a base URL configured via credentials to connect to the messaging API.
- Proper permissions are needed to delete message threads through the API.
Troubleshooting
- Invalid or missing Id: If the provided Id is empty or incorrect, the API will likely return an error indicating that the resource was not found. Ensure the Id corresponds to an existing message thread.
- Authentication errors: If the API key or credentials are invalid or expired, the node will fail to authenticate. Verify that the API key is correctly set up and has the necessary permissions.
- Permission denied: Even with valid credentials, the user or token might lack permission to delete threads. Check the API user roles and permissions.
- Network issues: Connectivity problems can cause request failures. Confirm network access to the API endpoint.
- API rate limits: Excessive requests might be throttled. Monitor usage and respect API limits.
Links and References
- Refer to the messaging platform’s official API documentation for details on deleting message threads.
- Consult n8n documentation on how to configure API credentials and handle HTTP request nodes for further customization.