Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Attachment → 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 Attachment resource with the Delete operation, it deletes an attachment record identified by its ID.
Common scenarios where this node is useful include automating CRM data management workflows, such as cleaning up obsolete or incorrect attachments in bulk, or integrating deletion of attachments as part of a larger automated process (e.g., when deleting related records).
Example use case: Automatically delete outdated or irrelevant attachments linked to CRM records during a scheduled cleanup workflow.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the attachment record to delete. This is required to specify which attachment will be removed. |
Output
The node outputs JSON data representing the response from the Twenty CRM API after attempting to delete the specified attachment. Typically, this will confirm successful deletion or provide error details if the operation failed.
- The output JSON structure corresponds to the API's response for the delete request.
- No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Twenty CRM API.
- The node uses the base API URL configured in the credentials.
- Network access to the Twenty CRM REST API endpoint is necessary.
Troubleshooting
- Invalid ID: If the provided ID does not correspond to an existing attachment, the API may return an error indicating the record was not found. Verify the ID is correct.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to delete attachments.
- Network issues: Connectivity problems can cause request failures; check network settings and API availability.
- JSON parsing errors: Not applicable for delete operation but relevant for other operations that accept JSON input.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- Twenty CRM API Documentation (general reference for API endpoints and authentication)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls