Twenty CRMInstall

Overview

This node integrates with the Twenty CRM API to perform various operations on CRM resources such as companies, people, opportunities, tasks, notes, calendar events, messages, attachments, workflows, and custom resources. Specifically, for the Attachment resource with the Get operation, it retrieves a single attachment record by its ID.

Common scenarios where this node is useful include:

• Fetching detailed information about a specific attachment linked to CRM records.
• Automating workflows that require accessing attachment metadata or content references.
• Integrating attachment data into other systems or processes without manual lookup.

Example: You have an attachment ID from a previous step or external source, and you want to retrieve its details (e.g., filename, size, related record) to process or display in your workflow.

Properties

Output

The node outputs JSON data representing the requested attachment record. The structure corresponds to the attachment object returned by the Twenty CRM API, typically including fields such as attachment metadata (e.g., filename, file type, size, creation date) and possibly links or references to the actual binary content.

If the node supports binary data output for attachments (not explicitly shown in the code), it would represent the actual file content; however, based on the static analysis, the node returns only JSON metadata for the attachment.

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 are indicated.

Troubleshooting

• Invalid ID: If the provided attachment ID does not exist or is malformed, the API will likely return an error. Ensure the ID is correct and corresponds to an existing attachment.
• Authentication errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
• Network issues: Connectivity problems can prevent successful API calls.
• Error messages: The node throws errors with messages from the API or internal validation. For example, if JSON parsing fails in other operations, it reports "Invalid JSON in Fields" — not applicable here but relevant for other operations.
• To continue processing other items despite errors, enable the "Continue On Fail" option in the node settings.

Links and References

• Twenty CRM API Documentation (general reference for API endpoints and data structures)
• n8n documentation on HTTP Request Authentication (for setting up API credentials)

This summary focuses solely on the Attachment resource's Get operation as requested.