TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node allows you to create a new note record in the connected service. It is useful for automating the creation of notes with specific content, titles, and metadata such as position and creator information. Typical use cases include logging information, adding comments or annotations programmatically, or integrating note-taking functionality into workflows.

For example, you could use this node to automatically generate meeting notes from calendar events or to add status updates as notes in a project management system.

Properties

Name Meaning
Depth Determines how much related object data 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.
Position Numeric value indicating the position of the note record. This can be used to order notes or specify placement.
Title The title of the note.
Body The main textual content of the note.
Body V 2 An alternative JSON-formatted body content for the note, allowing structured data instead of plain text.
Created By JSON object describing the creator of the note record, typically including user identification details.

Output

The node outputs a JSON object representing the newly created note record. The structure includes all properties sent during creation along with any additional metadata returned by the API, such as unique identifiers or timestamps. If the Depth property is set higher than 0, related objects will also be included in the output according to the specified nesting level.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the external service's API that manages notes.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL for the API is dynamically set from the credential domain configuration.

Troubleshooting

  • Common issues:

    • Invalid JSON format in Body V 2 or Created By fields may cause parsing errors. Ensure valid JSON strings are provided.
    • Missing required authentication credentials will result in authorization errors.
    • Providing invalid values for Depth or other properties might lead to unexpected responses or errors.

  • Error messages:

    • "Unauthorized" or "Authentication failed": Check that the API key or token is correctly configured and has necessary permissions.
    • "Invalid JSON" or "Unexpected token" errors: Validate JSON input fields before sending.
    • "Bad Request": Verify that all required fields like Title and Body are properly set and conform to expected formats.

Links and References

  • Refer to the external service’s API documentation for detailed information on note creation endpoints and supported fields.
  • JSON validation tools can help ensure correct formatting of complex input fields like Body V 2 and Created By.

Discussion