Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Actions46

Custom → Get Many

AI-generated

Overview

This node connects to the Twenty CRM API and allows users to perform various operations on different resources, including a "Custom" resource type. Specifically for the Custom - Get Many operation, it retrieves multiple records from a specified custom resource in the Twenty CRM system.

Typical use cases include:

  • Fetching lists of custom data entities such as blocklists, workflows, or views stored in Twenty CRM.
  • Retrieving filtered or ordered collections of custom records for reporting or further automation.
  • Integrating custom CRM data into other workflows by pulling batches of records with pagination support.

For example, you might use this node to get all entries from a custom resource called "workflows" to analyze workflow statuses or to sync them with another system.

Properties

Name Meaning
Custom Resource Name The plural name of the custom resource to query (e.g., "blocklists", "workflows", "views").
Return All Whether to return all available results or limit the number of returned records.
Limit Maximum number of records to return if not returning all (minimum 1).
Additional Options Collection of optional parameters:
- Order By Field name to order the results by.
- Order Direction Direction of ordering: "Ascending" or "Descending".
- Filter JSON JSON-formatted filter query to restrict which records are returned.

Output

The output is an array of JSON objects representing the retrieved records from the specified custom resource. Each object corresponds to one record with fields as defined by the custom resource schema in Twenty CRM.

If the node is set to return all results, it handles pagination internally and concatenates all pages into a single output array.

No binary data output is produced by this operation.

Dependencies

  • Requires connection credentials to the Twenty CRM API, specifically an API key or token configured in n8n.
  • The node uses HTTP requests authenticated via these credentials to communicate with the Twenty CRM REST API endpoint.
  • No additional external dependencies beyond the Twenty CRM API and n8n credential setup.

Troubleshooting

  • Invalid JSON in Fields / Filter JSON: If the filter or fields JSON input is malformed, the node throws an error indicating invalid JSON. Ensure that JSON inputs are correctly formatted.
  • API Authentication Errors: Failure to authenticate with the Twenty CRM API will result in errors. Verify that the API credentials are correctly configured and valid.
  • Resource Not Found: Specifying a non-existent custom resource name may cause the API to return errors or empty results. Confirm the exact plural resource name used in Twenty CRM.
  • Pagination Limits: When Return All is false, the node limits results to the specified Limit. To retrieve more records, enable Return All.
  • Network Issues: Connectivity problems can cause request failures. Check network access and API availability.

Links and References

Discussion