Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Workflow → Get Many
AI-generatedOverview
This node integrates with the Twenty CRM API to manage workflow records and other CRM resources. Specifically, for the Workflow resource with the Get Many operation, it retrieves multiple workflow records from the CRM system. It supports fetching all workflows or limiting the number of results returned, with options to filter and order the data.
Common scenarios include:
- Retrieving a list of workflows to display in dashboards or reports.
- Automating processes that require bulk access to workflow data.
- Filtering workflows based on specific criteria to trigger further actions.
Example: Fetching all workflows ordered by creation date descending to analyze recent activities.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all workflow records or only up to a specified limit. |
| Limit | Maximum number of workflow 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., "createdAt", "name"). |
| - Order Direction | Direction of ordering: Ascending or Descending. |
| - Filter JSON | JSON-formatted filter query to narrow down the workflows returned (e.g., {"status":"active"}). |
Output
The output is an array of JSON objects representing workflow records retrieved from the Twenty CRM API. Each object corresponds to a single workflow and contains its properties as provided by the API.
If binary data were involved (not applicable here), it would be included separately, but this node focuses on JSON data.
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 interact with the API.
- No additional external dependencies are required.
Troubleshooting
- Invalid filter JSON error: If the filter JSON is malformed, the node throws an error indicating invalid JSON. Ensure the filter is valid JSON syntax.
- API authentication errors: If credentials are missing or incorrect, requests will fail. Verify the API key credential is properly set up.
- Limit and Return All conflicts: Setting a limit while also enabling Return All may cause unexpected behavior; use these options correctly.
- Network or API downtime: Connectivity issues or API unavailability will cause request failures; check network and API status.
Links and References
- Twenty CRM API Documentation (example link, replace with actual)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling)
This summary covers the static analysis of the node's execute method for the Workflow resource's Get Many operation, focusing on input properties, output structure, dependencies, and common troubleshooting points.