Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Person → Delete
AI-generatedOverview
This node integrates with the Twenty CRM API to manage various CRM resources such as people, companies, opportunities, tasks, notes, and more. Specifically for the Person resource with the Delete operation, it deletes a person record identified by a given ID from the CRM system.
Common scenarios where this node is useful include:
- Automating cleanup of outdated or incorrect contact records.
- Integrating with other systems to remove contacts when they are deleted elsewhere.
- Managing CRM data lifecycle programmatically within workflows.
Example: Automatically delete a person record in Twenty CRM when a user unsubscribes from a mailing list.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the person record to delete. This is required to specify which person to remove. |
Output
The output JSON contains the response from the Twenty CRM API after attempting to delete the specified person record. Typically, this will be an empty object or confirmation of deletion depending on the API's behavior.
If the node encounters an error during deletion, the output may contain an error message describing the failure.
No binary data 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 details to be configured via credentials.
- Network access to the Twenty CRM REST API endpoint is necessary.
Troubleshooting
- Invalid ID: If the provided ID does not exist or is malformed, the API will return an error. Verify the ID is correct.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to delete person records.
- Network issues: Connectivity problems can cause request failures; check network and proxy settings.
- API rate limits: Excessive requests may be throttled by the API; implement retry logic or reduce request frequency.
- JSON parsing errors: Not applicable for delete operation but relevant if using other operations with JSON input.
Links and References
- Twenty CRM API Documentation (general reference for API endpoints and usage)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling in n8n)