Resources · n8n integration

Raindrop n8n integrationAutomate Raindrop with n8n.

Bookmarks pile up faster than anyone reads them. The Raindrop n8n integration exposes 13 operations across 4 resources: bookmarks, collections, tags and the account behind them. No Raindrop trigger ships with n8n, so a schedule or another app starts the run. Made for people who file links all day.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Raindrop n8n integration actually cover?

The Raindrop node talks to the Raindrop API from inside an n8n workflow, so saving a link stops being a manual gesture. It handles 4 resources: Bookmark, Collection, Tag and User, for a total of 13 operations. Everything a workflow needs to file a link, sort it into a collection, retag it later or clear it out is there, and one OAuth2 credential covers all of it.

Start with capture. A Schedule Trigger runs every morning, pulls fresh links from a feed or another app, and bookmark.create files each one under the right collection with tags already applied. That is the shape of the public template that pushes new items from a YouTube playlist into Raindrop, workflow 1217 on the n8n site, and the same pattern works with any source that returns a URL.

Then housekeeping, which is where most of the value hides. bookmark.getAll reads back every link in a collection, a filter node sorts the dead weight from the keepers, and bookmark.update retags the rest or moves it elsewhere. Links that no longer resolve go through bookmark.delete. Tags drift the same way: tag.getAll lists what exists, tag.delete removes the duplicates and typos, either everywhere or inside one collection.

Third pattern, reporting. collection.getAll lists the collections, a loop calls bookmark.getAll on each, and the result lands in a spreadsheet or a database. Pair it with Google Sheets for a weekly reading log, or with Notion when the research library already lives there. A short digest posted to Slack closes the loop for a team that shares sources.

Some things the node does not do. There is no search operation, no highlights, no import or export. When the Raindrop API offers an endpoint the node skips, the HTTP Request node calls it directly and reuses the same Raindrop credential through predefined authentication, so no second app registration is needed.

Two limits worth knowing before you build. Raindrop has no trigger node in n8n, which means nothing starts on its own: a Schedule Trigger at a fixed interval, an n8n Webhook (a URL another service calls), or a trigger from a different app has to open the workflow. And Return All matters on every list operation, because without it n8n stops at the value set in Limit. If the node is new to you, the n8n review covers the platform itself, and the n8n training goes through building a workflow step by step.

Connect

How do you connect Raindrop to n8n?

  1. 01

    Create a Raindrop app

    You need a Raindrop account first. Inside Raindrop, open Settings, go to Integrations, find the For Developers section and select + Create new app. That app is what issues the keys n8n will use. Raindrop supports one authentication method here, OAuth2, so there is no API key path to fall back on.

  2. 02

    Register the redirect URL

    Open a new Raindrop credential in n8n (Credentials menu) and copy the OAuth Redirect URL it displays. Paste that value into your Raindrop app as a Redirect URI and save the app. This is the address Raindrop sends you back to once you approve access, and it has to match exactly on both sides, character for character.

  3. 03

    Paste the client keys

    Back in the Raindrop app, copy the Client ID and the Client Secret, then enter both in the n8n credential and complete the connection. A credential is created once and reused by every workflow afterwards: the Raindrop node simply offers it in its dropdown, so a second workflow needs no setup at all.

Actions

The 13 operations of the Raindrop node

The Raindrop node exposes 13 operations across 4 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateDelete
Bookmark✓✓✓✓✓
Collection✓✓✓✓✓
Tag✓✓
User✓

Bookmark

5 operations
01

Create a bookmark

bookmark.create

What you see in n8n

Notes & use cases

Saves a URL into Raindrop and returns the new bookmark, ready to reference in the next node.

Key parameters

  • Link: the URL to save, the only required field, often {{ $json.url }} coming from the node before it.
  • Collection Name or ID: pick the destination collection from the list, or pass an ID with an expression.
  • Parse Metadata: tells Raindrop to load the cover, description and HTML for that URL instead of storing a bare link.
  • Tags: one string, several tags separated by commas.
Use cases
a feed watcher that files every new article under a topic collection, tagged at the moment of capture.
02

Delete a bookmark

bookmark.delete

What you see in n8n

Notes & use cases

Removes one bookmark from the account. The operation is scoped to a single item, so a cleanup loop runs it once per link.

Key parameters

  • Bookmark ID: the ID of the bookmark to delete. It comes from an earlier read rather than from the Raindrop interface, typically {{ $json._id }} after a list operation.
Use cases
a monthly pass that checks saved links with an HTTP Request node and drops the ones answering 404, so the collection stays trustworthy.
03

Get a bookmark

bookmark.get

What you see in n8n

Notes & use cases

Reads a single bookmark and returns its stored fields, including what Raindrop parsed from the page.

Key parameters

  • Bookmark ID: the identifier of the link to retrieve. Store it when the bookmark is created and the rest of the workflow can come back to it any time.
Use cases
an approval flow where someone submits a link, the workflow saves it, waits, then reads the record back to check the title and cover before announcing it anywhere.
04

Get many bookmarks

bookmark.getAll

What you see in n8n

Notes & use cases

Lists the bookmarks held in one collection, which is the entry point of every audit or export workflow.

Key parameters

  • Collection Name or ID: required here, since the operation reads one collection at a time. Choose it from the list or resolve it with an expression.
  • Return All: on, n8n walks through the API pages and brings back every link; off, it stops at Limit.
Use cases
a quarterly export of a research collection into a spreadsheet, where a truncated list would quietly lose sources.
05

Update a bookmark

bookmark.update

What you see in n8n

Notes & use cases

Edits a bookmark already saved. Only the fields filled in the Update Fields section change, the rest stays untouched.

Key parameters

  • Bookmark ID: which bookmark to edit, the single required field.
  • Collection Name or ID: set it to move the link into another collection.
  • Important: marks the bookmark as a favorite.
  • Order: its sort position, 0 pushing it to first place.
Use cases
a triage workflow that reads an inbox collection, then files each link and flags the ones worth reading first.

Collection

5 operations
06

Create a collection

collection.create

What you see in n8n

Notes & use cases

Opens a new collection, the folder Raindrop sorts bookmarks into, and hands back its ID for the operations that follow.

Key parameters

  • Title: the collection name, the only mandatory input.
  • Parent ID: the ID of the parent collection when this one should nest inside another.
  • Public: makes the collection reachable without authentication.
  • View: its display style, list, simple, grid or Masonry.
Use cases
a client onboarding that spins up a shared collection per project, nested under one parent, before anything is saved into it.
07

Delete a collection

collection.delete

What you see in n8n

Notes & use cases

Drops a collection from the account. Run it knowingly: the workflow gets no confirmation step, it simply executes.

Key parameters

  • Collection ID: the identifier of the collection to remove. A plain string here, so read it with a list operation rather than guessing it from the collection name.
Use cases
an archiving routine that exports a finished project's links elsewhere, then clears the collection so the sidebar reflects what is actually live.
08

Get a collection

collection.get

What you see in n8n

Notes & use cases

Returns one collection with its stored properties, useful whenever a workflow needs to confirm a target before writing to it.

Key parameters

  • Collection ID: the collection to retrieve, given as a string.
Use cases
a guard at the top of an import flow that reads the destination collection first, and routes to an alert instead of saving hundreds of links into a collection that was renamed or emptied since last run.
09

Get many collections

collection.getAll

What you see in n8n

Notes & use cases

Lists collections, and asks you to say which level of the tree you mean.

Key parameters

  • Type: required, either parent for root-level collections or children for the nested ones. Two calls are needed to map the whole tree.
  • Return All: brings back the full list by paging through the API, otherwise Limit caps it.
Use cases
a nightly inventory that lists every collection, then loops over them to count what each one holds.
10

Update a collection

collection.update

What you see in n8n

Notes & use cases

Changes the settings of an existing collection without touching the bookmarks inside it.

Key parameters

  • Collection ID: the collection to edit.
  • Title: its new name.
  • Cover: careful, on this operation the field takes the name of the binary property holding the image data, not a URL.
  • Sort Order: its descending position among collections sharing the same parent ID.
Use cases
a release routine that renames a working collection and flips Public on once the research behind it is ready to share.

Tag

2 operations
11

Delete a tag

tag.delete

What you see in n8n

Notes & use cases

Removes tags from the account, either across everything or inside a single collection.

Key parameters

  • Tags: one or more tags to delete, comma separated for several at once.
  • Collection Name or ID: optional, and it narrows the removal to that one collection instead of the whole account.
Use cases
a taxonomy cleanup that kills the accumulated variants of the same idea, singular and plural, capitalized and not, in one execution instead of dozens of clicks.
12

Get many tags

tag.getAll

What you see in n8n

Notes & use cases

Returns the tags in use, which is how a workflow discovers what the library is actually labeled with.

Key parameters

  • Collection Name or ID: a filter, to list only the tags found inside one collection.
  • Return All: off by default, so the node stops at Limit and a long tag list comes back cut.
Use cases
feeding a dropdown or a report with live tag values, rather than a hardcoded list that drifts from reality within weeks.

User

1 operation
13

Get a user

user.get

What you see in n8n

Notes & use cases

Reads account details from Raindrop, handy as a first test right after connecting the credential.

Key parameters

  • Self: a checkbox for returning details on the logged-in user, the account behind the credential.
  • User ID: the identifier of the user to retrieve. Both fields are marked required on this operation, so an empty one stops the execution.
Use cases
a smoke test node at the start of a workflow that confirms the OAuth2 connection still answers before the write operations run.
Need help

Need help automating Raindrop with n8n?

A person reads every message.

FAQ

Raindrop and n8n, the questions that come up

01Is the Raindrop n8n integration free in n8n?
Yes. The Raindrop node ships with n8n, so there is nothing to install and nothing extra to pay on the n8n side. It behaves the same on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance installed through Docker or npm under the Community Edition and its Sustainable Use license. A workflow built in one place runs unchanged in the other. All 13 operations are available either way. What a Raindrop account itself costs is a separate question and is not covered here, since it depends on the plan you hold with Raindrop.
02What credentials do you need for the Raindrop node?
One OAuth2 credential, which is the only authentication method Raindrop supports in n8n. OAuth2 means Raindrop sends you to its own login screen to approve access, then hands n8n a token instead of a password. You need a Raindrop account, and an app created from Settings, then Integrations, then Create new app in the For Developers section. That app gives you a Client ID and a Client Secret to paste into the n8n credential, and it must carry the OAuth Redirect URL copied from n8n as a Redirect URI. Once saved, the credential is reusable across every workflow.
03What are the limits of the Raindrop node in n8n?
The node covers 13 operations spread over 4 resources: Bookmark, Collection, Tag and User. Anything outside that list is not there, including search, highlights and bulk import or export. When the Raindrop API exposes an endpoint the node skips, the HTTP Request node calls it directly and reuses the same credential through predefined authentication. Two details catch people out. List operations return a capped number of items unless Return All is enabled, and on the update operation the Cover field expects the name of a binary property, not an image URL. Get a user also requires both of its fields.
04Does Raindrop react in real time in n8n?
No, and it cannot. Raindrop has no trigger node in n8n, so nothing on the Raindrop side wakes a workflow up. You start it another way. The Schedule Trigger runs the workflow at a fixed interval, every hour or every morning, and reads what changed since last time with a list operation. The n8n Webhook node gives you a URL that another service calls, which suits a form or an automation platform that can post to it. The trigger of another app works too: a new row, a new message, a new email can all open a workflow that then writes into Raindrop.
05n8n or Make for automating Raindrop?
It depends on what you weigh. Make is hosted only and bills per operation, so a workflow that lists hundreds of bookmarks costs more as it grows. n8n runs on its own Cloud or on your own server, which matters when the data should stay on infrastructure you control, and its pricing does not count individual steps the same way. Make leans harder into a visual, linear canvas. n8n mixes the visual canvas with code nodes and the HTTP Request fallback, which is exactly what you want the day an operation is missing from the Raindrop node. Neither is wrong, the hosting question usually decides.