Connect Obsidian

≈ 3 min Extension Bearer Token

Before you start

• The Obsidian desktop app, open while the workflow runs.
• The Local REST API community plugin.
• The AWFlow browser extension. These steps run in the extension (the web app hands them to it).

Used by

• Obsidian

Set it up

1. Install the plugin. In Obsidian, open Settings › Community plugins, browse for Local REST API, install it and enable it.

2. Turn on the HTTP server. In the plugin’s settings, enable the non-encrypted (HTTP) server on port 27123. The HTTPS port 27124 uses a self-signed certificate that the browser rejects.

3. Copy the API key from the plugin’s settings.

4. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap Obsidian in the list, then fill the rest.

   12345

   1. 1 Step 1:Pick Obsidian Under Integration App / Service, pick Obsidian. There is no Auth Type menu: Obsidian uses a Bearer Token.
   2. 2 Step 2:Name it For example Obsidian – vault. A Description is optional.
   3. 3 Step 3:Paste the key Paste the key into Bearer Token.
   4. 4 Step 4:Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Step 5:Click Create Credential Check: the credential is listed on the Credentials page, ready to pick in nodes.

   Numbered areas in the screenshot: 1. Integration App / Service: Obsidian; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

Check it's connected — 

Run Search vault with a word from one of your notes: the note comes back.

Where your token lives

Where your token lives — 

The credential is stored where you choose when you create it:

• Local (this browser only): encrypted in this browser. The encryption key is kept on the same device, so turn on the local secret vault to lock it with a passphrase only you know.
• Cloud (synced to your account): sent over an encrypted connection and stored encrypted on AWFlow’s server, so it works on your other devices.

When a step runs, your browser sends it only to your own computer (http://127.0.0.1:27123 by default). AWFlow’s servers never relay the call.

Privacy & your data →

Common issues

• “Could not reach the Obsidian Local REST API at…”. Obsidian is closed, the plugin or its HTTP server is off, or Server URL doesn’t match the port.
• “401 … check the API key from the plugin settings”. The key was regenerated in the plugin. Copy it again.
• The run is blocked in the web app. Obsidian runs through the browser extension. Install the extension and allow Obsidian for this workflow when asked, or run the workflow from the extension. See Extension-only integrations in the web app.

Related

Obsidian node

All connections

Create and manage credentials

Privacy & your data