Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Company → Get Many
AI-generatedOverview
This node integrates with the Twenty CRM API to manage company records. Specifically, the Get Many operation for the Company resource retrieves multiple company records from the CRM system. It supports fetching either all available companies or a limited subset, with options to filter and order the results.
Typical use cases include:
- Synchronizing company data from Twenty CRM into another system.
- Retrieving a filtered list of companies based on specific criteria (e.g., domain name, employee count).
- Exporting company lists for reporting or analysis.
For example, you might use this node to fetch all companies ordered by their creation date in descending order, or to retrieve only the first 100 companies matching a certain filter.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching company records or limit the number of results returned. |
| Limit | Maximum number of company records to return if not returning all. |
| Additional Options | Collection of optional parameters: |
| - Order By | Field name to order the results by (e.g., "name", "createdAt"). |
| - Order Direction | Direction of ordering: "Ascending" or "Descending". |
| - Filter JSON | JSON-formatted filter query to restrict which companies are returned (e.g., {"employees": {"$gt": 10}}). |
Output
The output is an array of JSON objects representing company records retrieved from Twenty CRM. Each object corresponds to a single company and contains fields as defined by the Twenty CRM API's company schema.
If the node is set to return all results, it will paginate internally until all matching companies 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 configured in the credentials.
- Network access to the Twenty CRM REST API endpoint is necessary.
Troubleshooting
- Invalid filter JSON error: If the filter JSON provided in Additional Options is malformed, the node throws an error indicating invalid JSON. Ensure the filter string is valid JSON.
- API authentication errors: If the API key credential is missing or invalid, requests will fail. Verify that the credential is correctly configured.
- Pagination limits: When Return All is enabled, the node paginates through results. If the API changes pagination behavior or limits, some records may not be retrieved.
- Rate limiting: Excessive requests may trigger API rate limits. Implement delays or reduce request frequency if encountering rate limit errors.
Links and References
- Twenty CRM API Documentation (example link; replace with actual)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling)
- JSON filtering syntax reference (depends on Twenty CRM API specifics)