Joplin icon

Joplin

Consume Joplin API

Actions9

Tag → Assign

AI-generated

Overview

This node allows you to assign a tag to a note in Joplin, an open-source note-taking and to-do application. The "Tag → Assign" operation is useful for organizing notes by categorizing them with tags, enabling easier searching and filtering within Joplin. For example, you might use this node in an n8n workflow to automatically tag new meeting notes with "meeting" or to categorize imported notes based on their content.

Properties

Name Type Meaning
Note Resource Locator Specifies the target note to which the tag will be assigned. You can select from a list, enter a URL, or provide the note ID directly.
Tag Resource Locator Specifies the tag to assign to the note. You can select from a list of available tags.

Output

The output is a JSON object containing the result of the tag assignment operation as returned by the Joplin API. The structure typically includes confirmation of the association between the tag and the note. Example:

{
  "res": {
    // Response data from Joplin's tagApi.addTagByNoteId method
  }
}
  • If the operation is successful, res contains details about the tag-note association.
  • No binary data is produced by this operation.

Dependencies

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

Troubleshooting

  • Invalid Note or Tag ID: If the provided Note or Tag ID is incorrect or does not exist, the node may throw an error such as "Not a valid Joplin Note ID" or "Not a valid Joplin note URL". Double-check that the IDs/URLs are correct and correspond to existing resources in Joplin.
  • Authentication Errors: If the credentials are missing or incorrect, you may receive authentication errors. Ensure your Joplin API token and base URL are set correctly in n8n credentials.
  • Connection Issues: If n8n cannot reach the Joplin API (e.g., due to network issues or the Joplin server being offline), the node will fail. Verify connectivity and that the Joplin Web Clipper service is running.

Links and References

Discussion