Open app

DocumentationWorkflowsTriggers

Anymize: Document processed node

Starts the workflow as soon as a document, text or URL has finished processing, including completed anonymizations. Optionally only for anonymizations or only on failures. 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 as soon as a document, text or URL has finished processing, including completed anonymizations. Optionally only for anonymizations or only on failures.

Use Anymize: Document processed 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: Document processed 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: Document processed has one focused purpose. Its available settings appear when you select the node.

Settings

FieldMeaningArea
On statusWhen the workflow should start.Standard
Anonymizations onlyOnly fire when the job is an anonymization.Standard
SourceDefault: Klartext recordings excluded (they have their own triggers).Standard
Only in projectOptional. Only jobs in this project.Standard
Filename containsOptional. Only jobs whose file or title name contains this text.Standard

Inputs and outputs

InputMeaningType
StandardThis trigger does not require an input.JSON
OutputMeaningType
job_idConfigure this value in the node panel.text
titleConfigure this value in the node panel.text
filenameConfigure this value in the node panel.text
statusConfigure this value in the node panel.text
sourceConfigure this value in the node panel.text
kindConfigure this value in the node panel.text
is_anonymizedConfigure this value in the node panel.boolean
project_idConfigure this value in the node panel.text
languageConfigure 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

{
  "job_id": "beispiel-job-id",
  "title": "Vertrag_2026.pdf",
  "filename": "Vertrag_2026.pdf",
  "status": "completed",
  "source": "",
  "kind": "",
  "is_anonymized": true,
  "project_id": "beispiel-projekt-id",
  "language": "de"
}

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