- Home
- Resources
- Integrations
- Raindrop
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
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.
How do you connect Raindrop to n8n?
- 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.
- 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.
- 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.
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.
| Resource | Create | Get | Get Many | Update | Delete |
|---|---|---|---|---|---|
| Bookmark | ✓ | ✓ | ✓ | ✓ | ✓ |
| Collection | ✓ | ✓ | ✓ | ✓ | ✓ |
| Tag | ✓ | ✓ | |||
| User | ✓ |
Operations index
Bookmark
5 operationsCreate a bookmark
bookmark.createWhat 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.
Delete a bookmark
bookmark.deleteWhat 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.
404, so the collection stays trustworthy.Get a bookmark
bookmark.getWhat 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.
Get many bookmarks
bookmark.getAllWhat 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.
Update a bookmark
bookmark.updateWhat 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,
0pushing it to first place.
Collection
5 operationsCreate a collection
collection.createWhat 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,gridorMasonry.
Delete a collection
collection.deleteWhat 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.
Get a collection
collection.getWhat 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.
Get many collections
collection.getAllWhat 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
parentfor root-level collections orchildrenfor 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.
Update a collection
collection.updateWhat 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.
Tag
2 operationsDelete a tag
tag.deleteWhat 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.
Get many tags
tag.getAllWhat 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.
User
1 operationGet a user
user.getWhat 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.
Need help automating Raindrop with n8n?
A person reads every message.



