top of page

Obsidian: Dynbedded

Hello and welcome.

Today I want to review Dynbedded.

Dynbedded will integrate content from other notes dynamically. This is valid for dataview queries, so it becomes easy to create a library of common queries, but also for date references. You can jump back and forth in time with Dynbedded.

The plugin was programmed by .... me .. but take a look yourself if I promise too much.

I assume in this post that you already know Obsidian and also know how to install community plugins. Feel free to leave comments if you have questions about this.


Dynbedded has two features:

  1. Embedding of dynamic content. The content embedded will reference the current note, not the note from which the content is coming from.

  2. Dynamic date substitution, for the current date but also for a relative date, so in the past or the future.

Let's take a look at some samples of the first feature:

Left Standard Embedded Feature / Right Dynbedded Embedded Feature

  • Dataview: shows inlinks into the note

  • Buttons: shows a note with 2 buttons

  • Buttons - Today: shows only the today button

And now the second feature:

  • Daily Note - Today: show the note which I embedded yesterday as TODAY

  • As you can see, Dynbedded doesn't support checking checkboxes natively

  • Daily Note - Last Week: show the information from last weeks note

So what are the pros / cons of Dynbedded?


  • Dynbedded allows usage of for example dataview queries in several notes. This is quite handy as it means you only need to change the query in one place instead of all over your vault.

  • Sure, you can use dataviewJS for it. But you need to know to program in javascript in this case, the other option is a lot easier.

  • And of course this also works with other features / plugins which require information from the current note.

  • The second feature with the dynamic date substitution was the main reason for me to write the plugin. I can display in a static note the content of yesterday, tomorrow, last week etc. without writing custom javascript code and can even look only at parts of that target note.

  • All of this fit's nicely into the concept of dashboard which don't need to be recreated all the time.


  • Dynbedded doesn't support tasks / checkboxes natively. You can use dataview though as a workarround.

  • The links which are used to embed the note are just text, not really links. So changing the target note will break the link.

What does it take to use Dynbedded?


Standard Syntax

For an easy embedded a codeblock is sufficient. (e.g. Dataview)

[[Title of Note]]

If you want to display only part of the note (z.B. Buttons- Today):

[[Title of Note#Header]]

Date Substitution

The usage for TODAY is quite simple, you only need to specify the format based on Moment.js date format.


You just need to specify the full note name inside the {{}}.

If you have a notename which doesn't only consist of a date, you need to specify this additional information too.


The other part of the name needs to be put into [].

Using relative date substitution might look complicated in the beginning but is quite easy:

First you use a P and afterward the difference of time you want to subtract or add to today.











If you want to show a note from 7 days ago you are either able to use:




Usage Example

Are there any examples on how to use Dynbedded?

Standard "Library"

You can use for example Dynbedded to embed standard dataview queries or buttons.

Create a note with a button per header and use Dynbedded to integrate the button where you like by embedding it via the header.

So, nothing is keeping you from creating the buttons at one place and using it all over the place instead of recreating the same button again and again.

The same works of course also with dataview queries, which are simpler to write then javascript queries.


And another example is a homenote / dashboard which uses relative dates to show specific information without the need to recreate the note again and again. This was my main reason to create the plugin.

An unfinished example.


If you want you can also change the style of the embeds. The following style sheet shows errors in red and the normal embeds in blue. But there is a lot more possible.

/* Sets all the dynbedded text color to blue! */
.dynbedded {
    color: blue;
/* Sets all the error text color to red! */
.dynbedded-error {
    color: red;

There are a lot of possibilities to let of steam and be creative.


What should I say. It does what is does, and as I'm using Buttons and Dataview I don't really notice the issue that I can't use Tasks / Checkboxes natively.

Noteworthy Tidbits

Gareth Stretton did describe on Medium an other workaround for centralised dataview queries, take a look.


So what do YOU think? Let me know, not only about the plugin but also about the review and the video.



bottom of page