Taskpath
← All guides

What Taskpath is and how it works

Taskpath handles the work that lands in shared folders and mailboxes, with governed AI. It runs over the tools your team already uses (email, shared folders on Nextcloud or WebDAV, web forms and webhooks) and doesn't move your work into Microsoft, Google or Atlassian.

The governed loop

Every request becomes a Task and moves through one loop, from arrival to done:

  1. It arrives. An email reaches a shared mailbox, a document lands in an intake folder, a form is submitted or a webhook fires. It becomes a Task.
  2. Read. Taskpath reads it and pulls out what matters. Fields taken from a document must be quoted from the document itself, or they're dropped.
  3. Match and route. Rules decide where it goes: which folder, which process, which person. A model reads and drafts; it doesn't decide where things go.
  4. Draft. It proposes a reply, a name and folder, or an answer, grounded in your approved sources and cited.
  5. A person approves. Anything that leaves the building, or can't be undone, waits for a person.
  6. Done, and on record. The approved action runs, and every step is written to the audit trail.

Earned autonomy

By default every proposal waits for a person. A person can let Taskpath act on its own for one kind of decision, such as filing a type of document or sending a kind of routine reply, and only when every check passes. For filing, Taskpath offers this after a run of approvals nobody had to change, and one undo switches it off again. High-impact actions are never automatic.

What makes it different

  • Narrow by construction. The AI gets one step at a time, not every tool. The checks around it are rules, not another model.
  • Permission-aware. With the Nextcloud app, Nextcloud's own permissions decide who can approve what: people approve only where they could have put the document themselves. The app does the filing inside Nextcloud; Taskpath never gets access to your Nextcloud.
  • Grounded, or it says so. Answers cite their sources, or Taskpath says it doesn't know.
  • EU-hosted. Taskpath is hosted in the EU and uses EU-hosted AI (Mistral). It reads only what a task needs. Self-hosting is not offered.

Where to start

Most teams start with one process:

  • Archive incoming documents. Documents dropped in an intake folder get a proposed name and folder, learned from your existing archive.
  • Handle support email or answer sales enquiries. A cited reply is drafted for each message and waits for a person to send it.
  • Capture and follow up leads. A signup is screened, a welcome is drafted for approval, and a follow-up is drafted if it goes quiet.
  • Answer questions from your docs. Cited answers from your knowledge base, or an honest "I don't know".