Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Actions46

Custom → Delete

AI-generated

Overview

This node integrates with the Twenty CRM API to manage various CRM resources, including a customizable "Custom" resource type. Specifically for the Delete operation on the Custom resource, it deletes a record identified by its ID from a user-specified custom resource collection (e.g., blocklists, workflows, views). This is useful when you want to programmatically remove entries from custom data sets managed within Twenty CRM.

Practical examples:

  • Deleting an obsolete workflow configuration from your CRM.
  • Removing an outdated blocklist entry.
  • Cleaning up custom views or other user-defined collections.

Properties

Name Meaning
ID The unique identifier of the record to delete.
Custom Resource Name The plural name of the custom resource collection from which to delete the record (e.g., blocklists, workflows, views).

Output

The output is a JSON array where each item corresponds to the result of the delete operation for each input item. Typically, the response contains confirmation of deletion or any returned data from the API after deletion.

If an error occurs during deletion and "Continue On Fail" is enabled, the output will include an object with an error field describing the issue along with the resource and operation names.

No binary data is produced by this node.

Dependencies

  • Requires connection to the Twenty CRM API via an API key credential.
  • The node expects the API URL and authentication token to be configured in the credentials.
  • Uses HTTP requests authenticated against the Twenty CRM API.

Troubleshooting

  • Invalid ID: If the provided ID does not exist or is malformed, the API may return an error. Verify the ID is correct.
  • Invalid Custom Resource Name: If the custom resource name is incorrect or does not exist in the CRM, the request will fail. Ensure the resource name matches exactly the plural form used in the API.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm that the API key credential is properly set up.
  • JSON Parsing Errors: Although not directly related to Delete, other operations involving JSON fields may throw errors if JSON is malformed.
  • API Rate Limits or Network Issues: These can cause request failures; check network connectivity and API usage limits.

Common error messages are passed through from the API and wrapped as node errors. Enabling "Continue On Fail" allows processing to continue despite individual item errors.

Links and References

Discussion