Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Actions46

Opportunity → Get Many

AI-generated

Overview

This node connects to the Twenty CRM API and allows users to retrieve multiple Opportunity records in bulk. The "Get Many" operation for the Opportunity resource fetches a list of opportunities with options to control pagination, filtering, and sorting.

Typical use cases include:

  • Synchronizing or exporting a list of sales opportunities from Twenty CRM.
  • Building dashboards or reports that require multiple opportunity records.
  • Automating workflows that process batches of opportunities based on specific criteria.

For example, you could use this node to get all opportunities currently in the "Negotiation" stage, ordered by their expected close date, or limit results to the top 100 most recent opportunities.

Properties

Name Meaning
Return All Whether to return all matching opportunity records or only up to a specified limit.
Limit Maximum number of opportunity 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., "closeDate", "amount").
- Order Direction Direction to order results: "Ascending" or "Descending".
- Filter JSON JSON-formatted filter query to restrict which opportunities are returned (e.g., by stage).

Output

The output is an array of JSON objects representing opportunity records retrieved from the Twenty CRM API. Each object corresponds to one opportunity and contains fields as defined by the API, such as:

  • name (Opportunity Name)
  • amount
  • stage
  • probability
  • closeDate
  • Other metadata fields provided by the API

If the "Return All" option is enabled and there are more pages of data, the node automatically paginates through all available results before returning them.

No binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the Twenty CRM API.
  • The node uses the base API URL configured in the credentials.
  • No additional external dependencies beyond the Twenty CRM API and n8n's HTTP request helper.

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: If the API key is missing or invalid, requests will fail. Verify the credential configuration.
  • Pagination Limits: When "Return All" is enabled, large datasets may take longer to fetch due to pagination. Consider using filters or limits to reduce data volume.
  • Field Names in Order By: Using incorrect or unsupported field names in "Order By" may result in unexpected ordering or errors. Confirm field names match those supported by the API.

Links and References

Discussion