Resources · Make integration

Diigo Make integrationAutomate Diigo with Make.

Stop copying links into Diigo by hand. The Diigo Make integration gives you 3 modules: two actions and one search. This page is for anyone who keeps research in Diigo, and it walks you from the connection to a first working scenario.

Try the Diigo integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Diigo Make integration do for you?

The Diigo Make integration links your Diigo account to Make, a tool where you build a scenario: an automation made of modules, each module being one brick such as an action or a search. With it, bookmarks land in your Diigo library, or come out of it, without you copying links by hand.

Keep every shared link. When a colleague posts an article in a chat app or a form collects a resource, Save a Bookmark files it in Diigo, so the reading list builds itself from the tools your team already uses.

Reuse your library elsewhere. List Bookmarks pulls bookmarks back out as bundles (one bundle is one item passing from one module to the next), which you can send to a sheet, a newsletter draft or a team channel.

Reach what the menu does not show. Diigo has no trigger in Make, and only two dedicated modules. For anything else, Make an API Call calls the Diigo API with the same connection. If you are still weighing tools, the n8n vs Make comparison lays out the differences, and the Make review covers the editor itself.

A caution before you start: the Make documentation for Diigo is short and flagged as AI-generated from the vendor docs, so check anything critical against Diigo itself. When a scenario refuses to run, the Make troubleshooting guide lists the usual causes.

Connect

How do you connect Diigo to Make?

  1. 01

    Grab your Diigo API key

    You need an active Diigo account and an API key. In Diigo, open the API Keys page from your account settings or the developer section, then copy the key shown on screen. Keep it at hand for the next step.

  2. 02

    Add a Diigo module

    In your Make scenario, add any Diigo module and click Create a connection. A connection is your Diigo account linked to Make once, then reused by every Diigo module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps if you manage several accounts. Paste the credentials you copied from Diigo, or follow the instructions Make shows on screen, and save.

First scenario

Your first scenario: file links from another app into Diigo

GoalWhen a link shows up in another app you use, Make saves it as a bookmark in Diigo.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Diigo has no trigger, so this first brick comes from the app where your links appear.

  2. 02

    Set up the starting module

    Search that other app by name, pick the module that brings in new items, and click Create a connection to link it. Fill its fields from the lists Make offers.

  3. 03

    Add Save a Bookmark

    Click the + on the right of the first module, search Diigo and choose Save a Bookmark. Connect your account, then map the link and its details from the previous module.

  4. 04

    Test with Run once

    Click Run once to run the scenario one time. Open each module to read the bundles it received, then check that the new bookmark sits in your Diigo library.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule: a new scenario runs every 15 minutes by default. Turn the scenario on and it keeps filing links without you.

Modules

What the Diigo modules do

Diigo gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Diigo1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module sends your own authorized request to the Diigo API, using the connection you already set up. It is the way to reach anything the two ready-made modules leave out, without building a separate login.

When to use it
you need a Diigo operation that neither Save a Bookmark nor List Bookmarks offers, and you can read the vendor API docs.
Watch out
you write the request yourself, so check the Diigo documentation for the exact path and parameters.
Diigo2

Save a Bookmark

Action

In Make“Saves a new bookmark.”

You get a new bookmark in your Diigo library each time the scenario reaches this action, filled with whatever the earlier modules pass along. It turns scattered links into one place you can search later.

When to use it
links arrive in another tool, such as a form reply or a shared message, and you want each one kept in Diigo automatically.
Watch out
it adds a bookmark on every run, so filter duplicates upstream if the same link can come back.
Diigo3

List Bookmarks

Search

In Make“Lists bookmarks.”

Your saved bookmarks come back out of Diigo so another app can use them. As a search module, it can return zero, one or many bundles, and every module placed after it runs once per bookmark.

When to use it
you want to push your research into a spreadsheet, a report or a team channel instead of copying it.
Watch out
each bookmark returned costs operations in the modules after it, and an empty result simply stops the chain.
Need help

Need help automating Diigo with Make?

A person reads every message.

FAQ

Diigo and Make: common questions

01Is the Diigo Make integration free?
Yes, Diigo is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. You still need your own Diigo account.
02What do you need to connect Diigo to Make?
You need an active Diigo account and a Diigo API key. Find the key on the API Keys page, reached from your account settings or the developer section, and copy it. In Make, add a Diigo module, click Create a connection, give it a name if you like, and paste the key. The connection is then shared by every Diigo module in your scenarios, so you only do this once per account.
03Does the Diigo Make integration have a real-time trigger?
No. Diigo has no trigger module in Make, neither scheduled nor instant. To start a scenario anyway, place a trigger from another app first, for example the app where links arrive, and follow it with a Diigo module. You can also start with List Bookmarks and let the scenario schedule decide when it runs, every 15 minutes by default, or as often as each minute on a paid plan. Test it with Run once before you switch it on.
04What if the Diigo module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Diigo API with the connection you already created, so you can reach actions that Save a Bookmark and List Bookmarks do not cover. You write the request yourself, so keep the Diigo API documentation open. Also note that the Make documentation for this app is marked as AI-generated from the vendor docs, so verify important details with Diigo directly.
05Should you use Make or n8n for Diigo?
It depends on the tool you already run. Apps like Diigo often have a node in n8n as well, so check that side before deciding. In Make, you get 3 ready modules for Diigo, including Make an API Call for the rest, and a Free plan with 2 active scenarios to test the idea. Pick the platform where the rest of your automations already live, since one connection per tool is easier to maintain than two.
Same platform

Other docs you might need on this stack.

Browse all integrations