Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Actions46

Person → Get Many

AI-generated

Overview

This node connects to the Twenty CRM API and allows users to perform various operations on CRM resources. Specifically, for the Person resource with the Get Many operation, it retrieves multiple person records from the CRM system. Users can fetch all persons or limit the number of results returned. Additional options allow ordering and filtering the results.

This node is useful in scenarios where you want to synchronize or analyze contact data stored in Twenty CRM, such as exporting a list of people for marketing campaigns, reporting, or integration with other systems.

Example use cases:

  • Retrieve all contacts (persons) in the CRM to export them to a mailing list.
  • Fetch a limited number of recent contacts ordered by last name.
  • Apply filters to get only persons from a specific city or with certain attributes.

Properties

Name Meaning
Return All Whether to return all matching person records or limit the number of results.
Limit Maximum number of person records to return if not returning all.
Additional Options Collection of optional parameters:
- Order By Field name to order the results by (e.g., "lastName", "firstName").
- Order Direction Direction of ordering: "Ascending" or "Descending".
- Filter JSON JSON-formatted filter query to restrict which persons are returned (e.g., by city, jobTitle).

Output

The output is an array of JSON objects representing person records retrieved from the Twenty CRM API. Each object corresponds to a person and contains fields as defined by the API, such as names, emails, phones, job titles, cities, etc.

If the node is configured to return all results, it handles pagination internally to accumulate all pages before outputting.

No binary data is output by this operation.

Dependencies

  • Requires connection credentials to the Twenty CRM API, including an API URL and authentication token.
  • The node uses n8n's HTTP request helper with authentication to communicate with the API.
  • No additional external dependencies beyond the Twenty CRM API and its credentials.

Troubleshooting

  • Invalid filter JSON error: If the filter JSON provided in Additional Options is malformed, the node will throw an error indicating invalid JSON. Ensure the filter is valid JSON syntax.
  • API authentication errors: If credentials are missing or invalid, requests will fail. Verify that the API key/token is correctly configured in n8n credentials.
  • Pagination issues: When returning all results, network interruptions or API limits may cause incomplete data. Consider limiting results or handling failures gracefully.
  • Limit value errors: Setting the limit below 1 will be rejected; ensure the limit is at least 1.

Links and References

Discussion