Comment #⁨1⁩

1000% — Tana is proving to be a game-changer for our organization. We use it for meeting notes and agendas, technical documentation, and ephemeral tasks that don't warrant an issue in our main issue tracker (Linear.)

For us, the benefits of an API would be huge, allowing Tana to act as a heads up display for things happening in other services (such as updates on Linear tasks, calendar agendas), as well as allowing Tana to feed data into other systems optimised for particular tasks.

Use cases, Tana -> Other Services

  • Watching for new or updated nodes with a certain tag, and syncing them to other services. Examples:
    • Pushing #tools from Tana to Airtable, which we use as a CMS.
    • Pushing #leads from Tana to our CRM and financial forecasts
    • Pushing issues to Linear
    • Drafting proposals and pushing them directly to our automated-proposal-generator
  • Creating embeddings or fine-tuning models based on our Tana database, enabling things like:
    • Conversational UI for solving customer support queries, based on our Tana documentation.
    • Automating proposal drafts based on meeting notes
  • Rolling our own front-end for our organizational operating system

Use cases: other services -> Tana

  • Using Zapier + OpenAI to summarise project updates/movements directly into our daily pages
  • Automatic feed of upcoming meetings in our daily/weekly pages

It would be a huge level-up for us! The flexibility of Tana's data structure is what attracted us to the service—in the medium-long term an API will be absolutely essential to our workflows.