Joplin icon

Joplin

Consume Joplin API

Actions9

Note → Get

AI-generated

Overview

The Joplin Note Get operation retrieves the details of a specific note from your Joplin instance using its unique identifier. This node is useful when you need to fetch and process the content or metadata of a particular note, for example, to display it in another system, trigger automations based on note content, or archive notes elsewhere.

Practical examples:

  • Fetching a note's content to send via email.
  • Syncing a Joplin note with another knowledge base.
  • Using note data as input for further workflow steps in n8n.

Properties

Name Type Meaning
Note Resource Locator The unique identifier of the note to retrieve. Can be selected from a list, entered as a URL, or by ID.

Details:

  • Note: Required. You can select the note from a searchable list, paste a Joplin note URL (e.g., joplin://x-callback-url/openNote?id=...), or enter the 32-character note ID directly.

Output

The output will be a JSON object containing all available fields of the requested Joplin note. Typical fields include:

{
  "id": "e167983d038548ed96e680b23f5254f1",
  "parent_id": "aabbccddeeff00112233445566778899",
  "title": "Sample Note Title",
  "body": "This is the note content.",
  "created_time": 1680000000000,
  "updated_time": 1680000001000,
  "user_created_time": 1680000000000,
  "user_updated_time": 1680000001000,
  "encryption_cipher_text": "",
  "encryption_applied": 0,
  "is_conflict": 0,
  "latitude": 0,
  "longitude": 0,
  "altitude": 0,
  "author": "",
  "source_url": "",
  "is_todo": 0,
  "todo_due": 0,
  "todo_completed": 0,
  "source": "",
  "source_application": "",
  "application_data": "",
  "order": 0,
  "tags": []
}
  • The actual structure may contain additional or fewer fields depending on your Joplin setup and note properties.
  • No binary data is returned; only structured JSON.

Dependencies

  • Joplin API: Requires access to a running Joplin instance with the Web Clipper API enabled.
  • Credentials: You must configure the jApi credential in n8n, providing the Joplin API base URL and token.

Troubleshooting

Common issues:

  • Invalid Note ID/URL: If the provided Note ID or URL does not match the required format, the node will throw an error such as "Not a valid Joplin note URL" or "Not a valid Joplin Note ID". Double-check the ID or use the list selector.
  • Authentication errors: If the API token or base URL is incorrect, you may receive authentication or connection errors. Ensure your credentials are correct and that the Joplin API is accessible.
  • Note not found: If the note does not exist, the node will return an error indicating the note could not be found.

How to resolve:

  • Use the resource locator dropdown to select the note if unsure about the ID.
  • Verify your Joplin instance is running and the API is enabled.
  • Check your credentials in n8n.

Links and References

Discussion