Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Message → Delete
AI-generatedOverview
This node integrates with the Twenty CRM API to manage various CRM resources such as companies, people, opportunities, tasks, notes, calendar events, messages, attachments, workflows, and custom resources. Specifically for the Message resource with the Delete operation, it deletes a message record identified by its ID from the Twenty CRM system.
Common scenarios where this node is useful include automating cleanup of outdated or irrelevant messages in your CRM, managing communication records programmatically, or integrating message deletion into broader workflow automations that maintain data hygiene.
For example, you might use this node to automatically delete notification messages after they have been processed or archived elsewhere, ensuring your CRM stays uncluttered.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the message record to delete. This is required to specify which message should be removed. |
Output
The output of the node is a JSON object representing the response from the Twenty CRM API after attempting to delete the specified message. Typically, this will confirm successful deletion or provide error details if the operation failed.
- The
jsonoutput field contains the API response. - No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Twenty CRM API.
- The node expects the API base URL and authentication to be configured via these credentials.
- Network access to the Twenty CRM REST API endpoint is necessary.
Troubleshooting
- Invalid ID: If the provided message ID does not exist or is malformed, the API will return an error. Ensure the ID is correct and corresponds to an existing message.
- Authentication errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
- API rate limits or downtime: Temporary issues with the Twenty CRM API may cause request failures. Retry later or check the service status.
- JSON parsing errors: Not applicable for delete operation but relevant for other operations involving JSON input.
If the node throws an error mentioning "Invalid JSON" or similar, it usually relates to other operations (like create or update) where JSON input is expected, not delete.
Links and References
- Twenty CRM API Documentation (general reference for API endpoints and usage)
- n8n Documentation on HTTP Request Node (for understanding how HTTP requests are made within n8n)
This summary focuses solely on the Message resource's Delete operation as requested.