Resources · Make integration

Raindrop.io Make integrationAutomate Raindrop.io with Make.

Can Make keep your Raindrop.io library moving without you? Yes. The Raindrop.io Make integration gives you 14 modules for bookmarks and collections, from spotting new ones to bulk imports. This guide connects your account, builds a first scenario and explains each module in plain words.

Try the Raindrop.io integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Raindrop.io Make integration do for you?

The Raindrop.io Make integration links your Raindrop.io account to Make so bookmarks and collections move on their own. A scenario, the automation you build in Make, can spot new items, create, update, list or delete them, and pass them to your other apps. You get 14 modules: 2 triggers, 9 actions and 3 searches, with no code to write.

A shared reading feed. Watch Bookmarks notices each new bookmark and hands it to the app your team reads, so a good article does not stay buried in one person's library.

A clean move from an old bookmark file. Parse HTML Bookmark File reads an HTML bookmark file, and Create a Bookmark recreates every entry in Raindrop.io, one bundle (one item passed between modules) at a time.

A reading space for each project. When a project opens in your CRM, Create a Collection prepares its collection. Watch Collections can then tell the rest of your tools that a new collection exists.

One thing Make does not offer for this app is an instant trigger. Both triggers are scheduled, so Make checks Raindrop.io at intervals rather than hearing from it the moment you save a link. For anything the listed modules skip, Make an API Call reaches the rest of the API with the same connection.

Weighing tools? The n8n vs Make comparison sets both side by side, and n8n often has a node for the same app. To plan your operations, read Make pricing, and if this is your first scenario, Make training starts from the basics.

Connect

How do you connect Raindrop.io to Make?

  1. 01

    Register an application in Raindrop.io

    In Raindrop.io, open the integrations section of your settings and click the button that creates a new application. Enter the callback URI given in the tip below, then copy the Client ID and the Client secret displayed on screen.

  2. 02

    Add a module and open the connection

    In Make, add any Raindrop.io module to your scenario and click Create a connection. Filling the Connection name field is optional, but a clear name helps once you link more than one Raindrop.io account.

  3. 03

    Paste your credentials and confirm

    Paste the Client ID and Client secret you copied, or follow the instructions Make shows on screen. The connection is your Raindrop.io account linked to Make once: every Raindrop.io module in every scenario reuses it.

First scenario

Your first scenario: send links from another app to Raindrop.io

GoalWhen a link shows up in another app, Make saves it as a new bookmark in Raindrop.io.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + to place the first module. Each module is one brick of the flow: a trigger, an action or a search.

  2. 02

    Pick where the links come from

    Search for the app where your links appear, such as a form or a spreadsheet, and choose its module. It starts the flow and hands each new item to the next module as a bundle.

  3. 03

    Add Create a Bookmark

    Click the + on the right, search for Raindrop.io and pick Create a Bookmark. Click Create a connection if needed, then map the data coming from the first module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Open Raindrop.io and check that the bookmark is there.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval allowed.

Triggers

What can start a Raindrop.io scenario?

2 modules start a scenario when something happens in Raindrop.io. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Raindrop.io as soon as it happens.

Raindrop.io1Watch Bookmarks

Watch Bookmarks

Scheduled trigger

In Make“Triggers when a new bookmark is created.”

Every new bookmark you save in Raindrop.io can start your scenario, so the links you collect travel on to other tools without anyone forwarding them.

How it fires
scheduled. Make checks Raindrop.io on the scenario's schedule, every 15 minutes by default. The Free plan cannot go below 15 minutes; paid plans go down to 1 minute.
When to use it
you save articles for your team and want each one posted where they already read, or logged in a shared sheet.
Watch out
Make describes it as firing on newly created bookmarks, so do not count on it to notice edits to older ones.
Raindrop.io2Watch Collections

Watch Collections

Scheduled trigger

In Make“Triggers when a new collection is created.”

A new collection in Raindrop.io becomes the starting signal of your scenario, which is useful when a collection stands for a client, a topic or a project.

How it fires
scheduled. Make asks Raindrop.io for new collections at each run of the scenario, based on its schedule, and nothing happens in between.
When to use it
someone opens a collection for a new research topic and you want a matching task or channel created elsewhere.
Watch out
it reacts to collections being created, not to bookmarks added inside them; pair it with Watch Bookmarks for that.
Modules

What the Raindrop.io modules do in Make

Raindrop.io gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Raindrop.io1

Create a Bookmark

Action

In Make“Creates a new bookmark.”

Your scenario saves a link into Raindrop.io for you, so a page spotted in another app ends up in your library with no copy and paste. Each run creates one bookmark from the data mapped earlier.

When to use it
a link arrives in a form reply or a spreadsheet row and belongs in your reading list.
Watch out
a new bookmark can also wake a Watch Bookmarks scenario on the same account, so keep the two flows apart.
Raindrop.io2

Create a Collection

Action

In Make“Creates a collection.”

A fresh collection appears in Raindrop.io as soon as your scenario needs a new home for links, for example one per client. The bundle it returns lets later modules reuse the new collection.

When to use it
a deal is won in your CRM and the client's reading space should be ready before the kickoff.
Watch out
to avoid a second collection for the same client, look it up with List Collections first.
Raindrop.io3

Delete a Bookmark

Action

In Make“Deletes a bookmark.”

Links that have done their job leave your library without a manual cleanup: this module removes one bookmark per run.

When to use it
a task is closed in your project tool and the reference link saved for it no longer needs to sit in Raindrop.io.
Watch out
treat every deletion as final and test on a throwaway bookmark with Run once before switching the scenario on.
Raindrop.io4

Delete a Collection

Action

In Make“Deletes a collection.”

When a project ends, its whole collection can go with it, keeping your Raindrop.io sidebar limited to work that is still alive.

When to use it
a project is archived in another app and its collection should disappear at the same moment.
Watch out
a wrong target costs more here than with a single bookmark, so check with Run once which collection the module receives before activating.
Raindrop.io5

Get a Bookmark

Action

In Make“Gets a bookmark.”

You get one bookmark in full, ready for the modules after it to reuse what Raindrop.io stores about that link.

When to use it
you already know which bookmark you want, for instance the one another module just pointed to, and a later step needs its details.
Watch out
it reads a single bookmark per run; to go through many of them, List Bookmarks is the better fit.
Raindrop.io6

Get a Collection

Action

In Make“Gets a collection.”

This module hands your scenario the details of a single collection, handy when a message or a report should describe the collection properly.

When to use it
an earlier module gave you a collection and the next step, such as a summary sent to a client, needs more about it.
Watch out
one collection per run; if you need the full picture, List Collections returns all of them as separate bundles.
Raindrop.io7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Whatever the ready-made modules leave out, this one lets you reach any endpoint of the Raindrop.io API, using the connection you already set up.

When to use it
an idea needs a Raindrop.io feature that none of the other modules on this page covers.
Watch out
you write the request yourself, so keep the Raindrop.io API documentation open next to Make while you build it.
Raindrop.io8

Update a Bookmark

Action

In Make“Updates a bookmark.”

Instead of saving a second copy, your scenario edits a bookmark that already exists, so the library stays clean when information about a link changes.

When to use it
a link reviewed in another tool needs correcting in Raindrop.io after the review.
Watch out
map the bookmark from Watch Bookmarks, Get a Bookmark or List Bookmarks earlier in the flow so the module edits the right one.
Raindrop.io9

Update a Collection

Action

In Make“Updates a collection.”

A collection keeps pace with the project it tracks, because the scenario edits it rather than building a new one.

When to use it
a client or a project is renamed in your CRM and its Raindrop.io collection should follow.
Watch out
point it at the right collection with List Collections or Get a Collection first; a change applied to the wrong one is easy to miss.
Raindrop.io10

List Bookmarks

Search

In Make“Lists bookmarks.”

Many links come back at once, each as its own bundle, so one run can review, export or clean a whole set of bookmarks.

When to use it
you want to copy a batch of saved links into a spreadsheet or check them one by one.
Watch out
each bundle makes the following modules run once more, and each of those runs is an operation counted on your Make plan.
Raindrop.io11

List Collections

Search

In Make“Lists collections.”

You see every collection your scenario can reach, one bundle per collection, which makes it easy to find the right one before acting on it.

When to use it
before Create a Collection, to check whether the collection already exists, or to build an overview of your library.
Watch out
a search can return zero bundles, so decide what the rest of the scenario should do in that case.
Raindrop.io12

Parse HTML Bookmark File

Search

In Make“Extracts importable bookmarks from an HTML bookmark file.”

An HTML bookmark file turns into bookmarks ready to import, each one coming out of the module as a separate bundle.

When to use it
you are moving an old stack of links into Raindrop.io; chain it with Create a Bookmark to recreate them one by one.
Watch out
a large file means many bundles, and therefore many operations for every module placed after this one.
Need help

Need help automating Raindrop.io with Make?

A person reads every message.

FAQ

Raindrop.io and Make: frequent questions

01Is the Raindrop.io Make integration free?
Yes. Raindrop.io is a standard app in Make, so all 14 of its modules work on the Free plan. That plan comes with limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) cut the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution, with usage counted in credits, meaning operations, each month. Your Raindrop.io subscription is separate and described on the Raindrop.io pricing page.
02What does it take to connect Raindrop.io to Make?
An active Raindrop.io account and an application registered in its settings. In the integrations section, you create a new application, enter the callback URI listed in Make's documentation for Raindrop.io, and copy the Client ID and Client secret shown on screen. Back in Make, add any Raindrop.io module, click Create a connection, give it a name if you want, then paste those credentials or follow the on-screen instructions. From then on, every Raindrop.io module reuses that connection.
03Are the Raindrop.io triggers in Make instant or scheduled?
Scheduled. Watch Bookmarks and Watch Collections are both polled: Make checks Raindrop.io on the scenario's schedule, instead of Raindrop.io calling Make through a webhook. A new scenario checks every 15 minutes by default. The Free plan cannot go below 15 minutes, while paid plans go down to 1 minute. In practice, a bookmark saved right after a check waits for the next one before anything happens. Make lists no instant trigger, the kind marked with a lightning badge, for this app.
04What if a Raindrop.io module is missing in Make?
Use Make an API Call. It calls any endpoint of the Raindrop.io API from your scenario with the connection you already created, so you are not limited to the ready-made modules. You write the request yourself, so keep the Raindrop.io API documentation at hand. Before going that way, look at the three searches, List Bookmarks, List Collections and Parse HTML Bookmark File: one of them may already return what you need, with far less setup than a raw request.
05Make or n8n for Raindrop.io?
It depends on what your scenario needs, not on a winner. In Make, Raindrop.io comes with 14 ready modules, 2 scheduled triggers and Make an API Call for the rest, all available on the Free plan. n8n often has a node for the same app too. The honest way to choose is to list the actions your flow requires, check that each tool covers them, and see which one your team already works in. The comparison page linked earlier on this page puts the two tools side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations