Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Note → Update
AI-generatedOverview
This node integrates with the Twenty CRM API to manage CRM data programmatically. Specifically, the Note - Update operation allows users to update an existing note record in their Twenty CRM system by specifying its ID and new content.
Typical use cases include:
- Modifying the title or body of a note attached to a CRM record.
- Automating updates to notes based on external triggers or workflows.
- Keeping CRM notes synchronized with other systems or data sources.
For example, you might use this node to update a meeting note's title and body after a call is completed, ensuring your CRM always has the latest information.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the note record to update. |
| Title | The updated title for the note. |
| Body | The updated content/body of the note, supporting multiline text (markdown format). |
Output
The node outputs JSON data representing the updated note record as returned by the Twenty CRM API. This typically includes the note's fields such as ID, title, body, timestamps, and any other metadata provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Twenty CRM API via an API key credential configured in n8n.
- The node uses HTTP PATCH requests to update records at the Twenty CRM REST endpoint.
- Proper API URL and authentication credentials must be set up in n8n for successful communication.
Troubleshooting
- Invalid JSON in Fields: Although not applicable directly to the Note resource update, if using custom resources with JSON fields, ensure that JSON input is valid to avoid errors.
- HTTP Errors: Common issues include invalid ID (record not found), insufficient permissions, or expired/invalid API credentials. Verify the note ID exists and credentials are correct.
- Empty Required Fields: The "Title" field is required; leaving it empty may cause the API to reject the update.
- Network Issues: Ensure n8n can reach the Twenty CRM API endpoint without firewall or proxy blocking.
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 further details about other operations or resources, feel free to ask!