⚡️ Ideas
Bill French Bill French Mar 1, 2023

Outbound Webhooks

Explain the problem you see

  • Nodes are bound to Tana
  • Exports are clunky and cumbersome
  • Copy/paste is limited to human actions in human UIs; some users want data flowing into database systems

Why is this a problem?

Tana is not the only system where note-taking, and sense-making occurrs, nor should it be a closed system.

Suggest a solution

Specific nodes should ideally broadcast changes to external endpoints. Users should be able to add a webhook to any node, and Tana would generate an HTTP POST to the designated endpoint, including all the data within that node.

The data payload format should be serialized Markdown within JSON.

⁨1⁩ ⁨Comment⁩

Absolutely ... was just coming to the ideas board to add exactly the same thing ... or at least very similar.

Maybe instead of having the webhook at the node level, it is held at the Supertag level ... so Supertags can optionally have a webhook flag ... and, when applied to a node, give that node webhook firing ability when created, changed, or deleted ... effectively CRUD webhook ability via Supertag application.