5 Tana Commands You Need To Know

Tana commands can turn routine service workflows—like handling daily coaching inquiries—into one-click, repeatable operations that automatically create tasks, projects, and follow-up timelines. Instead of manually copying the same steps into every new inquiry, the system uses commands to insert standardized SOP tasks, prefill fields, and route work based on what the client requested. That matters because service businesses lose quality and speed when intake, payment, scheduling, and status tracking depend on individual effort rather than automation.

The workflow starts when a service inquiry lands in Tana (for example via an input API connected to a website form). Each inquiry is tagged with details such as the service requested, the client identity, the context, and the chosen package (coaching or workspace setup). From there, one command—built as an “add SOPs” action—clones a set of predefined notes into new tasks. In the coaching case, those inserted tasks include sending a payment link and scheduling the coaching call after payment. The command is created by defining a command node that inserts cloned copies of referenced notes, then running it from the inquiry node.

To make this usable without memorizing command names, the setup adds a button to the inquiry configuration. Clicking the button runs the command and inserts the correct tasks. When there are multiple service types, the approach scales by using node filters: the same “add SOPs” button can insert different SOP tasks depending on fields like “service requested.” For coaching inquiries, the filter selects nodes where the service requested equals “Tana coaching,” while workspace setup uses a different filter (e.g., “Tana workspace setup”). This avoids cluttering the interface with multiple buttons that do the same structural job.

Next comes project creation. A second key command (“insert Tana paste,” used via a construction crane button) sets the service status to “in progress” and generates a delivery project automatically. Under that project, it creates coaching call nodes and populates the attendee field with the client’s name. It also builds live searches for prior coaching calls with the same attendee, so the system automatically surfaces what was discussed in earlier engagements. The command uses parameterized references to fields on the current inquiry node (using the dollar-sign and curly-brace syntax) so each new client gets correctly prefilled projects and searches.

The automation extends beyond structure into time management. A “complete” action sets a follow-up date relative to the current day—using an “insert relative date” operation—so fields can be set to “in two weeks,” “this week,” “tomorrow,” or “in two months” without manual date calculations.

Finally, commands can be composed together. By nesting one command inside another, a single button click can trigger both SOP task insertion and the deeper project-building logic from the construction crane command. The result is a layered workflow where intake, task execution, project tracking, historical context, and follow-up scheduling all snap into place with minimal repeated work.