Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Task → Delete
AI-generatedOverview
This node integrates with the Twenty CRM API to manage various CRM resources such as companies, people, opportunities, tasks, notes, and more. Specifically, for the Task resource with the Delete operation, it deletes a task record identified by its ID from the Twenty CRM system.
Common scenarios where this node is useful include automating cleanup of completed or obsolete tasks in your CRM, integrating task management workflows, or synchronizing task deletions from other systems into Twenty CRM.
For example, you might use this node in an automation that removes tasks marked as "Done" after a certain period, ensuring your CRM stays up-to-date without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the task record to delete. This is required to specify which task should be removed. |
Output
The node outputs JSON data representing the response from the Twenty CRM API after attempting to delete the specified task. Typically, this will confirm successful deletion or provide error details if the operation failed.
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 task ID does not exist or is malformed, the API will return an error. Ensure the ID is correct and corresponds to an existing task.
- Authentication errors: If the API key credential is missing, invalid, or expired, requests will fail. Verify that the credential is properly set up and has sufficient permissions.
- Network issues: Connectivity problems can cause request failures. Check network settings and API availability.
- API rate limits: Excessive requests may trigger rate limiting. Implement retries or backoff strategies if needed.
- Error messages: The node throws errors with messages returned by the API or internal HTTP request failures. Review these messages to identify issues.
Links and References
- Twenty CRM API Documentation (general reference for API endpoints and usage)
- n8n Documentation (for general node usage and credential setup)