Twenty CRMInstall

Overview

This node integrates with the Twenty CRM API to manage various CRM resources such as companies, people, opportunities, tasks, notes, calendar events, messages, attachments, workflows, and custom resources. Specifically, for the Attachment resource with the Update operation, it allows updating an existing attachment record by its ID.

Common scenarios where this node is beneficial include automating updates to CRM records during workflows, such as modifying attachment metadata or related information without manual intervention. For example, you might update an attachment's details after processing a file or changing its association within your CRM system.

Properties

Note: The provided properties JSON only includes the "ID" property relevant for update operations on the Attachment resource.

Output

The node outputs JSON data representing the updated attachment record returned from the Twenty CRM API. The structure corresponds to the API's response for the updated resource, typically including fields like the attachment's ID, name, URL, metadata, and other relevant attributes.

If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs an error object containing the error message along with the resource and operation names.

The node does not output binary data for this operation.

Dependencies

• Requires an API key credential for authenticating with the Twenty CRM API.
• The node uses HTTP requests to communicate with the Twenty CRM REST API endpoint specified in the credentials.
• No additional external dependencies are needed beyond the configured API authentication.

Troubleshooting

• Invalid ID: If the provided ID does not correspond to an existing attachment, the API will likely return an error indicating the record was not found. Verify the ID is correct.
• Invalid JSON (for custom fields): Although not applicable directly to Attachment update here, if using custom resources with JSON fields, malformed JSON will cause errors.
• Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to update attachments.
• Network Issues: Connectivity problems can cause request failures; verify network access to the Twenty CRM API.
• Error Messages: The node throws errors with messages from the API or internal validation. Enabling "Continue On Fail" allows workflow continuation with error details in output.

Links and References

• Twenty CRM API Documentation (general reference for API endpoints and data structures)
• n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)

If you need details on other operations or resources, feel free to ask!