TwentyDEVInstall

Overview

This node operation deletes a single message channel identified by its unique ID. It is useful in scenarios where you need to programmatically remove a specific communication channel from a messaging platform or service, for example, cleaning up unused channels or managing channel lifecycle automatically.

Properties

Output

The output JSON will typically contain the response from the API indicating the result of the deletion operation. This may include confirmation of successful deletion or details about any error encountered. The exact structure depends on the underlying API but generally confirms whether the specified message channel was deleted.

No binary data output is expected from this operation.

Dependencies

• Requires an API key credential to authenticate requests to the Twenty API.
• The node uses the Twenty API base URL configured via credentials.
• The node depends on the @devlikeapro/n8n-openapi-node package and the Twenty API OpenAPI specification bundled as twenty-v1.0.3-openapi.json.

Troubleshooting

• Missing or invalid Id: If the "Id" property is not provided or incorrect, the API will likely return an error indicating that the resource could not be found or the request is invalid. Ensure the correct channel ID is supplied.
• Authentication errors: If the API key or domain credentials are missing or invalid, authentication will fail. Verify that the credentials are correctly set up in n8n.
• API errors: The API might return errors if the channel does not exist or has already been deleted. Handle such cases gracefully in your workflow.
• Network issues: Connectivity problems can cause request failures. Check network access and API availability.

Links and References

• Twenty API Documentation (Assumed based on the node name; replace with actual link)
• n8n Documentation on Creating Custom Nodes