Building a User Feedback System with Tana and Pipedream

Standing on the verge of a new creation is an exhilarating experience for a Tana Builder. This is precisely where I find myself as I prepare to introduce the world to my latest brainchild, the Contextual Hierarchy template.

While I was busy with the process of refining and testing, a sudden idea came to my mind. I wanted to make it as easy as possible for beta testers to share their thoughts and feedback on the new template. No complicated logins, no shuffling through Discord channels, just a simple, straightforward way to send their thoughts my way.

The Context Hub in Contextual Hierarchy. Ready to be tested by Tana Nodes Gold members before public release in July.

The answer, it turned out, was simpler than I had initially imagined. It was a neat, user-friendly solution that required no code and just a few minutes of setup. Enter the feedback supertag, a built-in feature of the template designed to facilitate seamless, hassle-free user feedback while we beta-test the whole thing.

The feedback supertag comes packed with a Name field, a Discord User field, and a command. This command forms the bridge between the user feedback and my workspace, transmitting a collection of system fields, alongside the user-provided ones, to a Pipedream webhook.

The webhook then forwards this information straight to my personal Tana workspace via the Tana Input API.

Setting up the Pipedream webhook was a breeze. With the webhook in place, I was all set to craft the ‘Send Feedback’ command. ℹ️ This command is included in the Advanced Settings of the feedback supertag, ensuring it’s always present whenever a new feedback node is created in the template.

The command itself is very simple. It employs the Pipedream webhook URL as its destination, and all it requires to function are three additional fields – the API method and Parse result allow it to operate as a POST request, with the response left unparsed (we don’t need to interpret it). The Payload field is the last piece of the puzzle.

While it’s possible to send the entire node using ${sys:context}, I opted for a more granular approach. Each field in the Payload is sent as a standalone variable, allowing me to incorporate them individually in the Tana Input API payload that I send back to Tana.

	"feedback": "${name}",
	"name": "${Name}",
	"discord": "${Discord User}",
	"node_url": "${sys:nodeURL}"

With everything set up, it was time for the moment of truth – the test run.

Boom. A simple click on the ‘Send Feedback’ button sent the data to the webhook, and almost immediately, a new request came up on Pipedream. And just like that, the request was in, complete with four different fields ready for work.

The next step in my feedback collection journey involved creating a new supertag within my personal workspace. This supertag is a key element in the machine, gathering all the feedback in a simple, efficient format that allows me to promptly respond to and assist the user.

The supertag’s Payload then helped me to create an HTTP Request on Pipedream, which faithfully delivers every new piece of feedback to my Tana workspace, neatly packaged in a #ch-feedback node.

Run cmd/control + k > Show API schema on the supertag title to open this modal

The final piece of the puzzle was setting up the HTTP Request on Pipedream. Along with the supertag payload, I also needed the Tana Input API endpoint URL and my Tana workspace’s API token.

Armed with all I needed, I was ready to put the system to the test. The result? A seamless integration that worked like a charm. ✨

In a true test of real-world application, I created a new feedback node within the template bundle. This simulation allowed me to experience a realistic scenario where a user receives the template, follows the instructions, and sends me feedback. And it works perfectly.

Suddenly, the problem was solved, and all within Tana’s ecosystem. My users now have a fast, efficient way to send their feedback without any context switching.

As I prepare for the beta launch of the Contextual Hierarchy template, set for this Friday, June 16th, I find myself loaded with excitement. This new template, a product of the invaluable assistance and use-case scenarios provided by three members of my Coaching Program, is so much more than a ‘second brain’ system.

It represents a paradigm shift in our approach to content creation and retrieval. In Contextual Hierarchy, everything is associated with a specific context. Only areas are directly linked to contexts, while everything else is connected through semantic functions. Each critical entity has its own hub, ensuring straightforward yet elevated workflows.

👾 If you haven’t already, I urge you to join our Discord server, as the beta launch event will be held there. The invite is always valid and awaits you in your welcome email.

The Contextual Hierarchy template is more than just a product; it is a testament to the power of collective thought and collaboration between myself and individuals whom I did not even know three months ago. I cannot express enough gratitude to the Tana Community for providing me with the opportunity to meet and assist so many people over the past eight months.

As I continue to explore and expand the capabilities of this awesome tool, I can’t wait to share more with you all. Stay tuned, and join us to help us shape the future of new amazing Tana products!