Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Actions46

Custom → Update

AI-generated

Overview

This node integrates with the Twenty CRM API to perform various operations on CRM data entities, including a customizable "Custom" resource type. Specifically for the Update operation on the Custom resource, it updates an existing record identified by its ID with new field values provided as a JSON object.

Typical use cases include:

  • Modifying records in custom-defined resources such as blocklists, workflows, or views.
  • Updating specific fields of a custom CRM entity without affecting other data.
  • Automating updates to CRM data based on external triggers or workflows.

For example, you might update a custom workflow's status or parameters by providing the workflow's ID and a JSON object describing the updated fields.

Properties

Name Meaning
ID The unique identifier of the record to update.
Custom Resource Name The plural name of the custom resource (e.g., "blocklists", "workflows", "views").
Fields JSON A JSON object containing the fields and their new values to update in the record.

Output

The node outputs an array of JSON objects representing the updated records returned from the Twenty CRM API. Each output item corresponds to one input item processed.

  • The json output contains the updated record data as returned by the API.
  • If an error occurs during processing and "Continue On Fail" is enabled, the output will contain an error object with the error message, resource, and operation details.
  • This node does not output binary data.

Dependencies

  • Requires connection to the Twenty CRM API using an API key credential configured in n8n.
  • The node uses HTTP requests authenticated via this credential to interact with the API endpoints.
  • No additional external dependencies are required.

Troubleshooting

  • Invalid JSON in Fields: If the JSON provided in the "Fields JSON" property is malformed, the node throws an error indicating invalid JSON. Ensure the JSON syntax is correct before running.
  • Record Not Found: If the provided ID does not correspond to an existing record, the API may return an error. Verify that the ID is correct.
  • Authentication Errors: If the API key credential is missing or invalid, authentication will fail. Confirm the credential configuration.
  • API Rate Limits or Network Issues: These can cause request failures; check network connectivity and API usage limits.
  • Use the "Continue On Fail" option to allow the workflow to proceed even if some items fail.

Links and References

Discussion