Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Task → Get Many

AI-generated

Overview

This node integrates with the Twenty CRM API to manage various CRM resources, including tasks. Specifically, the "Task" resource with the "Get Many" operation allows users to retrieve multiple task records from their Twenty CRM account. It supports fetching all tasks or limiting the number of returned tasks, with options to filter and order the results.

Common scenarios for this node include:

  • Retrieving a list of tasks assigned to a user or team for reporting or dashboard purposes.
  • Filtering tasks based on specific criteria such as status or due date.
  • Exporting tasks data for further processing or integration with other systems.

For example, a sales manager might use this node to fetch all tasks marked as "In Progress" ordered by due date ascending, helping prioritize daily work.

Properties

Name Meaning
Return All Whether to return all matching task records or limit the number of results.
Limit Maximum number of task records to return (used only if "Return All" is false).
Additional Options Collection of optional parameters:
- Order By Field name to order the results by (e.g., due date, status).
- Order Direction Direction of ordering: "Ascending" or "Descending".
- Filter JSON JSON-formatted filter query to narrow down the tasks returned (e.g., filtering by status).

Output

The output is an array of JSON objects representing task records retrieved from the Twenty CRM API. Each object corresponds to a single task and contains fields as defined by the API, such as title, body, status, due date, and other task-related metadata.

If binary data were involved (not in this operation), it would be summarized accordingly, but here the output is purely JSON data.

Dependencies

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

Troubleshooting

  • Invalid Filter JSON: If the filter JSON provided in "Additional Options" is malformed, the node will throw an error indicating invalid JSON. To resolve, ensure the filter string is valid JSON syntax.
  • API Authentication Errors: If the API key credential is missing or invalid, authentication errors will occur. Verify that the API key is correctly set up in n8n credentials.
  • Limit Exceeded: When "Return All" is false and a very high limit is set, the API may restrict the number of returned items. Adjust the limit or enable "Return All" to fetch all pages.
  • Network Issues: Connectivity problems with the Twenty CRM API endpoint can cause request failures. Check network connectivity and API service status.

Links and References

Discussion