Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Note → Get
AI-generatedOverview
This node integrates with the Twenty CRM API to manage various CRM resources such as companies, people, opportunities, tasks, notes, and more. Specifically, for the Note resource with the Get operation, it retrieves a single note record by its unique ID.
Typical use cases include:
- Fetching detailed information about a specific note attached to a CRM record.
- Automating workflows that require accessing note content or metadata.
- Integrating note data into other systems or reports.
For example, you might use this node to get the contents of a note linked to a customer interaction and then send that information via email or log it in another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the note record to retrieve. This is required for the Get, Update, and Delete operations. |
Output
The node outputs the retrieved note data as JSON. The structure corresponds to the note object returned by the Twenty CRM API, typically including fields like the note's title, body content (possibly in markdown), creation date, and any associated metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Twenty CRM API.
- The node expects the API base URL and authentication details to be configured in the credentials.
- Network access to the Twenty CRM REST API endpoint is necessary.
Troubleshooting
- Invalid ID error: If the provided note ID does not exist or is malformed, the API will return an error. Ensure the ID is correct and corresponds to an existing note.
- Authentication errors: If the API key credential is missing, invalid, or expired, requests will fail. Verify the credential configuration.
- JSON parsing errors: Although not typical for the Get operation, if any JSON input is malformed (in other operations), the node throws an error indicating invalid JSON.
- API rate limits or connectivity issues: Network problems or API limits may cause request failures. Check network connectivity and API usage quotas.
If the node is set to continue on failure, errors for individual items will be returned in the output JSON under an error field.
Links and References
- Twenty CRM API Documentation (general reference for API endpoints and data structures)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are made within n8n nodes)