---
name: workist-docs
description: Workist docs (docs.workist.com) — channels, fields, thresholds, assistance, validation, master data, SFTP/AS2/API. Use for Workist setup/support questions and before planning Workist implementations.
---

# Workist docs

docs.workist.com is the source of truth and changes often. Answer from pages fetched in this
conversation, not from memory: Workist terms (channel, assistance, filling, partition, discard)
have product-specific meanings, and a plausible-sounding guess produces wrong configuration advice.

## Find the right page

1. Fetch the index that matches the user's language:
   - English: https://docs.workist.com/en/llms.txt
   - German: https://docs.workist.com/llms.txt
   Each line links one page with a short description.
2. Pick the 1–2 most relevant pages and fetch their links from the index. Don't construct
   URLs yourself; the paths in the index are authoritative.
3. German is the source language and English can lag behind. If an English page has nothing
   beyond its heading, fetch the same page from the German index.
4. If the docs don't cover the question, say so and suggest contacting Workist. Never invent
   settings, labels or default values.

Top-level sections, for orienting: Implementation Guide, Channel Configuration (General,
Incoming Documents, Document Processing, Exported Processed Documents), Data Exchange,
Smart Inbox, Master Data, API Documentation, Output Formats, FAQ.

## Before implementing anything

When planning, scoping or building a Workist feature, customer-specific logic, a workaround or a
ticket, first check the docs for whether it's already possible via configuration (channel
configuration, validation checks, assistance keywords, field mappings, master data, filling,
document filtering, discard rules, output formats). Configuration beats code: no deploy, the
customer can maintain it, and no special case lands in the codebase.

- Search for the requirement in product terms, not code terms ("always send rush orders to
  manual review" → Document → Validation → Keywords for Assistance).
- Report one of: fully possible via configuration (path and settings), partially possible
  (what's covered, what's missing), or not documented.
- "Not documented" doesn't mean "not possible": the docs can lag the product. Say so, and if the
  codebase is available, check the configuration models there too.
- Only then plan the implementation, and build only the gap.

## Answer

- Give the UI path with exact labels, e.g.
  **Channel Configuration → Document Processing → Document → Validation**.
- Use setting names exactly as the docs write them.
- Link the human-readable page: the fetched URL without the `.md` extension, with a trailing slash.
- Where the docs say a setting is configured together with Workist (e.g. automation thresholds),
  say so, and don't encourage customers to change it on their own.
- Keep it short: answer, path, link. Reproduce option tables only when the user needs the full list.
- Reply in the user's language.