Open app

DocumentationWorkflowsTriggers

Anymize: Knowledge base ready node

Starts the workflow when a knowledge base has enough processed documents, by default only once processing has fully completed. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

7 min readUpdated

What this node does

Starts the workflow when a knowledge base has enough processed documents, by default only once processing has fully completed.

Use Anymize: Knowledge base ready as a clearly defined step in an anymize workflow.

  • Starts a new workflow run.
  • Provides one output for following steps.
  • Runs as a regular step in the flow.

Set up the node

  1. 01Open a workflow and add Anymize: Knowledge base ready from the node catalog.
  2. 02Complete the required fields and map values from previous steps.
  3. 03Run the node with a small test record and inspect its output.
  4. 04Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Anymize: Knowledge base ready has one focused purpose. Its available settings appear when you select the node.

Settings

FieldMeaningArea
At least N documents processedOnly fire once this many files are fully processed.Standard
Only when fully completedOff = fire already during processing, as soon as the minimum count is reached.Standard

Inputs and outputs

InputMeaningType
StandardThis trigger does not require an input.JSON
OutputMeaningType
knowledge_base_idConfigure this value in the node panel.text
nameConfigure this value in the node panel.text
processed_docsConfigure this value in the node panel.number
total_docsConfigure this value in the node panel.number
rag_statusConfigure this value in the node panel.text

Example and test run

Test-run example: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "knowledge_base_id": "beispiel-datenbank-id",
  "name": "Produktwissen",
  "processed_docs": 12,
  "total_docs": 12,
  "rag_status": "completed"
}

Access and security

Before activation, review which data enters this step and what its output contains.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

  • No output: inspect the latest run and confirm that the previous node returned the expected fields.
  • Empty variable: open the previous step output and use a field name from the real test data.
  • Workflow does not start: activate it and check the trigger's test and production mode.

Related articles