Docs

How DocuBots works

Describe a document problem, refine a visual workflow, and publish a hosted app your team can run.

Overview

DocuBots is Qualetics Nautilus, specialized for documents. You describe a document job in Ask. The product scaffolds a workflow on a visual canvas and a hosted operator app. Qualetics DataMachines do the extraction, classification, generation, and related work.

How it works

  1. Sign up and open Ask.
  2. Describe the problem, or pick a starter such as invoice desk or contract review.
  3. Open the canvas to refine nodes: extract, classify, review, generate, compliance.
  4. Publish the hosted app so operators can upload, submit, and watch runs.
  5. Attach automations so runs start from a schedule, webhook, upload, or app submit.

Solutions

Starters are not a static template gallery. They are catalog solutions that create a real workflow and app in your tenant. Browse them on the solutions page, then create them from Ask.

Visual workflows

Workflows are graphs of document steps. You can start from Ask or from a blank canvas. Runs execute through Qualetics agents, with optional human review and compliance checks. Generated documents can attach back to the run.

Hosted apps

A Document App is a published UI schema: pages of widgets such as file upload, form, run status, results, document viewer, and review queue. The app is branded for your organization. Operators use the hosted URL instead of the studio.

Automations

Triggers can start a workflow run from:

  • A cron schedule
  • An incoming webhook
  • A document upload
  • A submit on the hosted app
  • An API call with an API key

Credits

New accounts receive 100 credits. Document processing typically uses 1 credit (3 with OCR). Image analysis starts at 5 credits. Generation varies by operation. Credits do not expire and there is no monthly seat fee. Buy packs in the product when you need more.

API

Every published app has an API, including apps you buy on the marketplace. Create an API key under Settings, then send documents from your own portal, ERP, or case system and collect the results. Each app's page in DocuBots shows its endpoint, its inputs, and ready-to-copy examples.

Run an app

POST /api/apps/{appId}/runs
x-api-key: db_...
Content-Type: multipart/form-data

file=@invoice.pdf
customerName=Acme        # one field per app input

→ 201 { "runId": "...", "status": "queued" }

Get the result

GET /api/apps/{appId}/runs/{runId}
x-api-key: db_...

→ 200 {
  "status": "completed",
  "result": { ... },
  "files": [{ "name": "summary.pdf", "url": "/api/documents/.../download" }]
}

GET /api/apps/{appId}/inputs lists the inputs an app expects. Apps that fill in a document template take a templateId from your account. For a bought app, the API returns results and files only. The creator's workflow stays private, and your documents stay in your organization.

If you built the workflow yourself, you can also start it directly with POST /api/workflows/{workflowId}/run. Exact paths and payloads are in the in-app API docs after you create an account.

Create an account