Connecting Diigo to Goji

Diigo is a research and bookmarking service rather than a social network, and that is exactly why it is useful here. Connecting it to Goji files every new article into your Diigo library automatically, with its description and tags, building a searchable archive of everything you publish without any manual filing.

What connecting Diigo gives you

• An automatic archive. Each new article is bookmarked with its title, description and tags.
• Real search. Diigo indexes what you save, so finding an article you published months ago takes seconds.
• Tags that carry over. Article tags become Diigo tags, which is how a library of any size stays navigable.
• Private or shared, your choice. Bookmarks can be kept private or made public, and you decide which when you connect.

Before you start

You need a Diigo account and an API key, which Diigo issues from its developer page. Unlike most channels here the connection uses your account username and password alongside that key, because Diigo offers no app-password mechanism.

That is worth a moment's thought: if you would rather not store your main account credentials, create a Diigo account specifically for this archive. It costs nothing and keeps the two separate.

How to get the API key

1. Sign in to Diigo in a browser.
2. Open Diigo's API key page from its developer documentation.
3. Request a key for personal use. Diigo issues one immediately.
4. Copy it and keep it private — it identifies your application to Diigo.

How to connect it in Goji

1. Open Channels from the sidebar and choose Diigo.
2. Enter your Diigo username and password.
3. Paste the API key.
4. Choose whether bookmarks should be shared (public in your library) or private.
5. Save. Goji checks the credentials with Diigo immediately, so a mistake is caught while you are still on the form.

What gets saved

Each bookmark carries the article's URL, its title, its summary as the description, and its tags. Diigo does not fetch the page's text itself, so what you see in your library is what was sent — which means the summary on your source article is doing real work here and is worth writing properly.

Because Diigo deduplicates by URL, re-saving the same article updates the existing bookmark rather than creating a second one.

If something goes wrong

• Sign-in was rejected. Check the username rather than the email address, and confirm the API key was copied in full.
• Bookmarks are public when you wanted them private. The shared option was left on. Change it on the channel and future bookmarks follow the new setting; existing ones keep whatever they were saved with.
• Tags are missing. The article had none. Add tags at the source and future saves will carry them.
• Nothing is arriving. Confirm the channel is enabled and included in your publishing rules — a private archive channel is easy to forget about.

Common questions

Is this a publishing channel? Only in the loosest sense. Nothing is broadcast; it files links into your library.

Can other people see my bookmarks? Only if you choose the shared option.

Does it replace an analytics or content log? No, but it is a genuinely useful record of what went out and when.

How do I stop it? Disconnect the channel. Everything already saved stays in Diigo.