Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Attachment → Get Many
AI-generatedOverview
This node integrates with the Twenty CRM API to manage various CRM resources, including Attachments. Specifically, the Attachment - Get Many operation retrieves multiple attachment records from the CRM system. It supports fetching all attachments or limiting the number of results, with options to filter and order the returned data.
Typical use cases include:
- Retrieving a list of attachments related to contacts, companies, or deals for reporting or processing.
- Exporting attachment metadata for backup or migration purposes.
- Filtering attachments by specific criteria (e.g., date range, type) to automate workflows based on attachment data.
Example: A user wants to fetch up to 100 attachments uploaded in the last month, ordered by upload date descending, to process them in another system.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching attachments or limit the number of results. |
| Limit | Maximum number of attachments to return if not returning all. |
| 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 restrict which attachments are returned (e.g., by date, type). |
Output
The output is an array of JSON objects representing attachment records retrieved from the Twenty CRM API. Each object contains the fields as provided by the API under the data property, such as attachment ID, filename, associated record IDs, creation date, and other metadata.
If the node is configured to return all results, it handles pagination internally to accumulate all pages before returning.
No binary data output is produced by this operation; it only returns metadata about attachments.
Dependencies
- Requires an API key credential for authenticating with the Twenty CRM API.
- The node uses HTTP requests to the Twenty CRM REST endpoints.
- No additional external dependencies beyond the Twenty CRM API and n8n's HTTP request helper.
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 invalid, the node will fail to authenticate. Verify that the API key credential is correctly configured.
- Pagination issues: When returning all results, network interruptions or API limits may cause incomplete data. Consider using the "Limit" option if encountering timeouts.
- Field names in Order By: Using incorrect or unsupported field names in the "Order By" option may result in empty or unexpected results. Confirm field names against the Twenty CRM API documentation.
Links and References
- Twenty CRM API Documentation
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)
- JSON Syntax Guide (for crafting valid filter JSON)