Notion

SimpleBackups is now capable of taking snapshots of your Notion resources, In this documentation, We’ll explore how to Add a new Notion connection to your SimpleBackups Account, Create a backup, and Restore it.

In order to get started, from your SimpleBackups Dashboard, you can search for notion in the Quick Access section of your Dashboard and click on the Notion tile.

To configure your new Notion connection, click on the Add button next to the dropdown, name your connection, and select the resources you’d want to make available to SimpleBackups.

SimpleBackups will backup all resources it has access to unless it’s instructed to exclude them.

In this example, we’re going to exclude a resource titled SimpleBackups from the backup job.

We’re almost there, all you need now is to configure the backup’s name (Make sure it’s named in a way where you can easily recognize it from other Notion backups.), Schedule, and Storage.

In my case, I’m going to make it run daily with a retention of 30, and name it Personal Notion Workspace Backup.

This step is completely optional, but it’s highly recommended with any backup configured on your SimpleBackups account.

After creating your backup you’ll be redirected to your backup’s summary page, in where you can run your backup On Demand by clicking the Run Now button.

When you find yourself in need of restoring your notion backup, you can easily do that by following these steps:

Navigate to your desired backup’s summary page and click on Logs

Then click on the the log you desire to restore to based on the time it has been taken, this will open a log summary popup

To restore, click on the Restore tab, and find the Restore Workspace button

This will begin the process of restoring your backup, which will run in the background so you can safely close this window.

After a while, you’ll be able to find your Backup in your workspace fully restored nested underneath a page titled something like this

Backup Restore: <BACKUP_NAME> (<BACKUP_DATE> - #<LOG_ID>)

With the variables in the angled brackets replaced with your actual Backup and Log information

SimpleBackups now offers the capability to back up and restore your Notion resources. By following the steps outlined in this guide, you can easily create a Notion backup, configure its settings, and restore it when needed. This ensures that your important Notion data is securely backed up and can be recovered without overwriting your existing workspace.

Due to some Notion API limitations, a complete Notion Workspace restore & backup is currently impossible. However we’re actively working on supporting Notion’s API updates.

An “unsupported” block in the Notion API can represent various situations where the API doesn’t know how to handle a particular block type. Here are some scenarios where this might occur:

1. New Block Types: Notion might introduce new block types after the version of the API you’re using was released. If the API hasn’t been updated to recognize these new types, it will mark them as “unsupported.”

2. Custom or Experimental Blocks: Notion may have blocks that are either custom or experimental and not yet part of the public API. These blocks would not be recognized by the API and therefore marked as “unsupported.”

3. Third-Party Integrations: If you have a Notion page that includes blocks generated by third-party integrations or plugins, these might not be recognized by the API and thus marked as “unsupported.”

4. Rich Media Content: Certain rich media content, like embedded widgets or files from services not natively supported by Notion, might be classified as “unsupported” if the API doesn’t know how to handle them.

5. Obsolete or Deprecated Blocks: If a block type is deprecated or no longer in use, but still exists in some Notion pages, the API might not recognize it and mark it as “unsupported.”

In order to include new notion pages in the backup, you’ll need to grant the SimpleBackups integration access to said pages.

To grant simplebackups access, follow these steps: