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 allows creating multiple notes in bulk via the "Create Many Notes" operation under the "Notes" resource. It is useful when you need to add several notes at once, for example, importing a batch of comments or annotations into a system that supports note-taking or record-keeping.
Practical examples include:
- Importing multiple customer feedback entries as notes.
- Adding a series of log entries or audit trail notes programmatically.
- Bulk creation of project or task notes from an external source.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested information to include in the response: - 0: Only the primary note object. - 1: The note plus its directly related objects. - 2: The note, its related objects, and their related objects. |
| Body | A JSON object representing the note(s) to create. This should contain the data structure expected by the API for one or many notes. |
Output
The output json field contains the response from the API after creating the notes. Depending on the Depth parameter, this will include the created note objects with varying levels of nested related data:
- At depth 0, only the basic note information is returned.
- At depth 1, the note plus its immediate related objects are included.
- At depth 2, the note, its related objects, and those objects' related objects are included.
If the API supports binary data for notes (e.g., attachments), it would be included accordingly, but based on the provided code and properties, the main output is JSON data representing the created notes.
Dependencies
- Requires an API key credential to authenticate requests to the Twenty API.
- The base URL for the API is configured dynamically from credentials.
- The node uses the Twenty API version 1.0.3 OpenAPI specification for request construction.
Troubleshooting
- Invalid JSON in Body: Since the Body property expects valid JSON, malformed JSON input will cause errors. Ensure the JSON is correctly formatted.
- Authentication Errors: Missing or invalid API credentials will result in authentication failures. Verify that the API key credential is properly set up.
- Depth Parameter Misuse: Using unsupported depth values may cause unexpected responses or errors. Use only 0, 1, or 2 as specified.
- API Limitations: Creating too many notes at once might hit API rate limits or payload size restrictions. Consider batching if errors occur.
Links and References
- Twenty API Documentation (general reference for the API)
- OpenAPI Specification (for understanding the API schema used)