Tana Input API: Bookmarking with Omnivore

In a world where data reigns supreme and my digital life flourishes in Tana, the introduction of the Tana Input API has been a game-changer. The API, designed for effortlessly populating Tana with structured data, represents a significant leap forward in integration capabilities. Even though the API is still in its early stages, its power and potential are already making waves. What’s more, the future roadmap promises exciting expansions, including the much-anticipated read capabilities.

In this guide, I will delve into a practical demonstration of the API’s capability. I will walk you through the process of setting up a bookmarking system with Omnivore and Make/Integromat. This hands-on approach will not only help you grasp the functioning of the Tana Input API but also inspire you to explore its endless potential. So, get ready to embark on a journey to master the Tana Input API and take your data management skills to the next level.

Getting Started with Tana Input API

Before we dive into the API, you need to generate an API token for your workspace in the Tana client. Here’s how you can do that:

  1. Click on ‘API Tokens’ located in the upper right corner of the Tana top-bar.
  2. Choose the workspace for which you want to create the token and click ‘create token’.

Note that the Tana Input API is designed with specific restrictions to ensure optimal performance. It permits only one call per second per token and allows a maximum of 100 nodes per call. The total characters in one request must not exceed 5000. These limitations are, of course, subject to change. Refer to this Github repo for updated informations.

Creating Webhooks in Make and Omnivore

To send our Omnivore saves to Tana, we need to create a new scenario in Make that will start with a Custom Webhook.

  • Once you have the URL, copy it.

Now, create a Webhook integration in Omnivore.

  • For this tutorial, we will look only for page created events. So paste the Make URL, select PAGE_CREATED in the event types, and create our Integration.

Creating a Bookmarking Supertag and copying the Payload Schema

We now need a structure for our bookmarks. The API Schema is available for ALL your supertags. I am creating a new supertag for this tutorial, but you are free to use one of your existing supertags Payload and use it for your integration.

As demonstrated in the video above, I am creating a Bookmark supertag where the structure includes title, description, author, URL, and a checkbox which I will then use as a “status” to filter bookmarks I have processed or that I simply want to keep active.

Creating an HTTP Request in Make

We’re now ready to create our HTTP request in Make so that we can send new #bookmarks to Tana when we save a URL to Omnivore.

  1. The new API endpoint is: https://europe-west1-tagr-prod.cloudfunctions.net/addToNodeV2
  2. Use the workspace “API Token” that we generated in the first step, and the Payload obtained via the supertag API schema.
  3. Once you have created the base request, run the scenario and save a link to Omnivore with their Chrome Extension. This way, you have a payload sent to the Webhook that you can use to customize your request.

To customize the request content (payload), simply select the fields you want to use in the fields of your bookmark supertag. The payload is exactly like the supertag structure, so after the node name, the first field will be the first field of your supertag. Each field has a unique ID, so keep track of it to ensure you’re adding the right data to the right field.

Now that your request is customized, it’s time to test the integration. The testing phase is crucial to ensure that your data is correctly and smoothly flowing from Omnivore into Tana. I am using Omnivore’s Chrome Extension.

Active Command

As mentioned above, I’m using the ‘Is Active’ checkbox field to filter bookmarks that I have processed or those I want to keep active. For this process to be efficient, a Command is precisely what we need. The simple command checks the state of the field; if it’s unchecked, the command button will be visible.

The Tana Input API represents a new chapter in the evolution of data management within Tana. With this guide, you’re equipped to make full use of it in your day to day.

On a personal note, since the introduction of the Tana Input API, my data management has transformed significantly. I’ve set up numerous integrations using the API, and the process has been nothing short of exciting and rewarding.

For instance, I’ve created a seamless connection with Stripe to track transactions and monitor financial data. My scheduling system on Cal.com is now linked with Tana, making it easy to keep track of my appointments and meetings. Omnivore integration has revolutionized my bookmarking system, making it easy to save and categorize web pages in Tana. Even my Airtable databases are now synced with Tana.

These integrations have not only streamlined my work processes but also made my day to day more enjoyable.

How do you plan to use the Tana Input API? What integrations are you excited to set up? I’m genuinely interested to hear about the unique and innovative ways you’ll bring your data to life in Tana. After all, the beauty of it all is in its versatility – it’s a tool that can be as unique and creative as you are. So go ahead, start exploring, and have fun!