Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Calendar Event → Get Many
AI-generatedOverview
This node connects to the Twenty CRM API and allows users to interact with various CRM resources, including Calendar Events. Specifically, for the Calendar Event resource with the Get Many operation, it retrieves multiple calendar event records from the CRM system.
Typical use cases include:
- Fetching a list of calendar events for reporting or synchronization purposes.
- Retrieving upcoming or past events filtered by specific criteria.
- Integrating calendar event data into workflows for automation, reminders, or notifications.
For example, a user might want to get all calendar events ordered by date in descending order or filter events based on certain JSON criteria such as event type or status.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching calendar events or limit the number of results returned. |
| Limit | Maximum number of calendar events to return if "Return All" is false. |
| Additional Options | Collection of optional parameters: - Order By: Field name to sort the results by. - Order Direction: Sort direction, either Ascending or Descending. - Filter JSON: JSON-formatted filter query to narrow down results. |
Output
The node outputs an array of JSON objects representing calendar event records retrieved from the Twenty CRM API. Each object corresponds to one calendar event and contains fields as provided by the API (e.g., event title, start/end times, description).
If the node is configured to return all results, it handles pagination internally to fetch all pages of data.
No binary data output is produced by this operation.
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 communicate with the Twenty CRM REST endpoints.
- No additional external dependencies are required.
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 credential is missing or invalid, authentication errors will occur. Verify that the API key is correctly set up in n8n credentials.
- Pagination Limits: When "Return All" is enabled, the node attempts to paginate through results. If the API changes pagination behavior or limits, some results may not be fetched. Adjust limits or filters accordingly.
- Network Issues: Connectivity problems to the Twenty CRM API endpoint can cause request failures. Check network access and API availability.
Links and References
- Twenty CRM API Documentation (for detailed API fields and filtering options)
- n8n Documentation on HTTP Request Node (for understanding HTTP request handling in n8n)