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 Message resource with the Update operation, it updates an existing message record in the Twenty CRM system by sending a PATCH request with the specified changes.

Common scenarios where this node is beneficial include automating updates to CRM messages based on external triggers or workflows, such as modifying message content, status, or metadata after receiving new information or completing related tasks.

Practical example: Automatically update the content or status of a message in Twenty CRM when a related event occurs in another system, ensuring that CRM data stays current without manual intervention.

Properties

Note: For the Message resource's Update operation, only the ID property is explicitly defined in the provided input properties snippet. However, the node’s code suggests that additional fields relevant to the Message resource could be updated if supported (not detailed here).

Output

The node outputs JSON data representing the updated message record returned from the Twenty CRM API. The output is structured as an array of JSON objects, each corresponding to an item processed by the node.

• The json field contains the updated message data as returned by the API.
• If the operation involves multiple items, the output includes metadata linking each output item to its input counterpart.
• The node does not output binary data for this operation.

Dependencies

• Requires an active connection to the Twenty CRM API via an API key credential configured in n8n.
• The node uses HTTP requests authenticated with this credential to perform operations on the Twenty CRM REST API.
• No other external dependencies are indicated.

Troubleshooting

• Invalid ID: If the provided message ID does not exist or is incorrect, the API will likely return an error indicating the record was not found. Verify the ID before running the node.
• Invalid JSON in Fields: Although not shown explicitly for Message update, if any JSON fields are used (as in custom resources), invalid JSON syntax will cause errors. Ensure JSON inputs are well-formed.
• Authentication Errors: If the API key credential is missing, expired, or invalid, authentication will fail. Confirm the credential configuration in n8n.
• API Rate Limits or Network Issues: Temporary failures may occur due to rate limits or connectivity problems. Retrying or checking network status can help.
• Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

• Twenty CRM API Documentation (general reference for API endpoints and data structures)
• n8n Documentation for configuring credentials and using HTTP Request nodes

If you need details about other properties or operations, please provide additional input property definitions or specify further.