Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Actions46

Note → Get Many

AI-generated

Overview

This node integrates with the Twenty CRM API to manage various CRM resources, including Notes. Specifically, the "Get Many" operation for the Note resource retrieves multiple note records from the CRM system. It supports fetching all notes or limiting the number of results, with options to filter and order the returned data.

Typical use cases include:

  • Synchronizing notes from Twenty CRM into another system.
  • Displaying a list of notes related to contacts or deals.
  • Automating workflows that require bulk processing or analysis of notes.

For example, you might use this node to fetch all notes created in the last month, ordered by creation date descending, to generate a report or trigger follow-up actions.

Properties

Name Meaning
Return All Whether to return all matching note records or only up to a specified limit.
Limit Maximum number of note records to return (ignored if Return All is true).
Additional Options Collection of optional parameters:
- Order By Field name to order the results by (e.g., "createdAt", "title").
- Order Direction Direction of ordering: "Ascending" or "Descending".
- Filter JSON JSON-formatted filter query to restrict which notes are returned (e.g., by date, status).

Output

The node outputs an array of JSON objects representing note records retrieved from Twenty CRM. Each object corresponds to a single note and contains fields as defined by the Twenty CRM API's note resource schema, such as title, body content, creation date, and other metadata.

If binary data were involved (not applicable here), it would be summarized accordingly, but this operation returns only JSON data.

Dependencies

  • Requires an API key credential for authenticating with the Twenty CRM API.
  • The node uses the base API URL provided by the credential configuration.
  • No additional external dependencies beyond the Twenty CRM API.

Troubleshooting

  • Invalid Filter JSON: If the filter JSON is malformed, the node throws an error indicating invalid JSON in the filter. Ensure the filter is valid JSON syntax.
  • API Authentication Errors: Failure to authenticate with the API will result in errors. Verify that the API key credential is correctly configured and has necessary permissions.
  • Limit Exceeded: When not using "Return All," setting a very high limit may cause performance issues or API rate limits. Use filters and ordering to optimize queries.
  • Pagination Handling: When "Return All" is enabled, the node automatically paginates through results. If the API changes pagination behavior, results may be incomplete.

Links and References

Discussion