Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node operation "Find One Note" retrieves a single note object by its unique identifier. It is useful when you need to fetch detailed information about a specific note, including optionally related nested objects depending on the depth level specified. Typical use cases include displaying or processing a particular note's content and metadata in workflows, or integrating note details into other systems.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the note to retrieve. This is required to specify which note to find. |
| Depth | Determines how much related nested data to include in the response: |
| - 0: Only the primary note object without any related objects. | |
| - 1: The note plus its directly related objects (no further nesting). | |
| - 2: The note, its directly related objects, and the related objects of those related objects (two levels). |
Output
The output JSON contains the full data of the requested note object. Depending on the Depth property, this includes:
- At depth 0: only the main note's fields.
- At depth 1: the note plus its immediate related objects.
- At depth 2: the note, its related objects, and their related objects as well.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential to authenticate requests to the Twenty API.
- The base URL for the API is configured via credentials.
- The node uses standard HTTP headers for JSON communication.
Troubleshooting
- Missing or invalid Id: If the Id property is empty or incorrect, the node will fail to find the note. Ensure the Id is correct and provided.
- Authentication errors: If the API key or domain credentials are missing or invalid, authentication will fail. Verify credentials are properly set up.
- Depth value issues: Providing a depth outside the allowed options (0, 1, 2) may cause unexpected results or errors. Use only the supported values.
- Network or API errors: Connectivity issues or API downtime can cause failures. Check network access and API status.
Links and References
- Twenty API Documentation (for more details on note objects and related entities)
- n8n documentation on Using API Credentials