Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Actions46

Custom → Get

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 Custom - Get operation, it retrieves a single record by its ID from a user-specified custom resource collection within Twenty CRM.

Typical use cases include:

  • Fetching detailed information about a specific custom entity (e.g., blocklists, workflows, views) stored in Twenty CRM.
  • Integrating custom CRM data into automated workflows, such as syncing or reporting.
  • Accessing custom resource records dynamically by specifying their plural resource name and record ID.

Example: Retrieve a workflow configuration stored as a custom resource named "workflows" by providing its unique ID.

Properties

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

Output

The node outputs the JSON representation of the requested custom resource record under the json field of the output item. This JSON contains all fields and values as stored in Twenty CRM for that particular record.

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the Twenty CRM API via an API key credential configured in n8n.
  • The node uses the base API URL provided by the credential to construct REST requests.
  • Proper permissions on the Twenty CRM account to access the specified custom resource and read records.

Troubleshooting

  • Invalid JSON in Fields: Although not directly relevant to the "Get" operation, other operations involving JSON input may throw errors if the JSON is malformed. Ensure JSON inputs are valid.
  • Record Not Found: If the provided ID does not exist in the specified custom resource, the API will likely return an error or empty response. Verify the ID and resource name.
  • Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Incorrect Custom Resource Name: The custom resource name must be the plural form as used in the API endpoint path. Misspellings or incorrect names will cause request failures.
  • Network Issues: Connectivity problems can cause HTTP request failures; verify network access to the Twenty CRM API.

Links and References

Discussion