Taskpath
← All guides

Channels, automations, and knowledge

Channels (how work gets in and out)

Everything that links Taskpath to the outside world lives under Connections. Inbound channels each turn a message into a Task:

  • Mailbox (IMAP). Email to a shared mailbox becomes a task.
  • Web form. A public form submission becomes a task.
  • Incoming webhook. An HMAC-signed webhook becomes a task.
  • Nextcloud app. Documents dropped in a shared intake folder become filing proposals. Install it from the Nextcloud App Store; it connects in two steps, and Nextcloud's permissions decide who can approve.
  • WebDAV folder. Files dropped in a watched folder become tasks.

Outbound is email (approved replies) and outgoing webhooks (to a CRM or other system). All inbound messages are normalized to one canonical record that the Activity feed reads.

Automations (how work gets done)

An automation is a declarative sequence of steps triggered by a channel event. Available step types include: interpret, extract, classify, retrieve, validate, clarify, consult, generate (governed assistant with RAG + citations), approve, execute, deliver, wait, and deterministic branches.

Automations start from templates and are switched on per workspace by a person. A typical support automation: interpret → classify → draft a cited reply → check it's supported → escalate to a person if not → wait for a person to review and send. Anything that leaves the building or can't be undone waits for approval, unless a person has switched on earned autonomy for that kind of decision (see "What Taskpath is and how it works").

Knowledge (what answers are grounded in)

Upload documents into the knowledge base (under Knowledge), optionally grouped into collections (e.g. support, sales) that the Assistant can be pointed at. Taskpath chunks and embeds them so the assistant can answer with citations. A WebDAV/Nextcloud connection can also feed its files into the knowledge base, but only if you switch on “Index files into knowledge” on the connector, so a folder used only for document intake never gets pulled into the KB by surprise. Good answers from resolved tasks can be captured back into the knowledge base (governed review), so the system gets better with use.

Knowledge and drafting require an AI provider to be configured for the workspace (Settings → AI). Taskpath supports Mistral and any OpenAI-compatible endpoint, so you can keep it EU-hosted.