Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Actions46

Message → Get Many

AI-generated

Overview

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

Typical use cases include:

  • Synchronizing messages from Twenty CRM into another system.
  • Displaying a list of messages in a dashboard or report.
  • Automating workflows based on message data retrieved from the CRM.

For example, you might use this node to fetch the latest 50 messages related to customer interactions or to retrieve all messages filtered by a specific criterion such as date or sender.

Properties

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

Output

The output is an array of JSON objects representing message records retrieved from the Twenty CRM API. Each object corresponds to a single message with its associated fields as provided by the API.

If the node is configured to return all results, it will paginate through the API responses automatically until all matching messages are fetched.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Twenty CRM API.
  • The node uses the base API URL from the credentials to construct requests.
  • Proper network access to the Twenty CRM API endpoint is necessary.

Troubleshooting

  • Invalid filter JSON error: If the "Filter JSON" property contains malformed JSON, the node will throw an error indicating invalid JSON. Ensure that the filter is valid JSON syntax.
  • API authentication errors: If the API key credential is missing or invalid, requests will fail. Verify that the credential is correctly configured.
  • Pagination issues: When returning all results, if the API changes pagination behavior or limits, the node may not retrieve all data. Check API documentation and update node configuration accordingly.
  • Limit property ignored when Return All is true: The "Limit" setting is only applied when "Return All" is false; otherwise, all available messages are fetched.

Links and References

Discussion