What gets detected?
Choose the language, region, data types and detection threshold. Use an allowlist for terms that should stay.
API · Projects · Headless
Your documents keep moving.
Sensitive data stays under control.
Make anonimize part of your existing process. Receive documents through the API, process them in the right project and let the anonymised or pseudonymised result continue to your next application.
With n8n, Power Automate, Zapier or your own software.
From source to destination
A place between input and what comes next.
Your workflow connects the steps. Anonimize processes the documents; your integration checks the status, retrieves the result and passes it on.
- Your source
Documents arrive
Files or text from a form, case file, storage system or your own application.
- Your rules
The right project
Project settings, access permissions and your chosen approach.
- API
anonimize processes
Detect, anonymise or pseudonymise through the API.
- Output
Processed result
Processed text or a new document, ready for the next step.
- Your destination
On with your process
To your application, or through further steps in your workflow first.
Start with a project
Set the rules first.
An administrator or authorised project lead configures the project. Your workflow can use its default settings, so each new document starts with the same chosen approach.
How is it replaced?
Choose anonymisation or pseudonymisation. For pseudonymisation, reuse a project key to preserve consistency across a case file.
Who gets access?
Use project permissions and an API key you can restrict to a single project. Give your integration only the permissions it needs.
Where does review fit?
Decide when someone should check the result. Protected document exports follow the configured permissions and export approval.
You choose the process
Run headless. Or bring in a colleague.
From a fully automated step to a process with review: choose a route that fits your documents and how the output will be used.
Without opening the interface
Headless through the API.
In a server-managed workspace, your integration submits files or text, follows processing and retrieves the result. After the initial setup, this can run without interacting with the app.
- A project and appropriate API permissions
- Check the status and retrieve the result
- Pass it on through your own workflow
With a review checkpoint
A person at the right moment.
Pause your workflow before the output goes any further. A colleague checks the detections and context; you then let the next step continue.
- Review in your configured process
- Separate export approval where needed
- Continue after your agreed release
Connect your way
Fits between the tools you already use.
Use the general HTTP or API steps in your workflow tool. They connect anonimize with applications that can receive files or text.
n8n
Connect your source using the HTTP Request node. Check the status, retrieve the output and use it in subsequent nodes.
Explore the HTTP Request nodePower Automate
Add the API to a cloud flow using HTTP actions or a custom connector. Pass the processed output to your Microsoft or other business applications.
Explore HTTP in Power AutomateZapier
Use general API or webhook actions to exchange data. Configure the next actions for the destination in your Zap.
Explore API steps in ZapierThe integration uses these tools’ general API capabilities. Available actions, file limits and licensing vary by tool and plan.
Your own application or integration partner?
The same API works from your own software. Receive processed text or retrieve an export, then decide how it moves on to your CRM, DMS, analytics environment or AI application.
What this can look like
From intake to useful information.
Prepare case files
A new file in document storage starts your workflow. The right project provides the defaults; the processed result returns to your case management system.
Send data to an AI application
Reports are processed before your workflow sends the text to a chosen AI application. You decide which information and context go along.
Process and distribute further
Let n8n, Power Automate, Zapier or your own code transform, enrich or route the output to several permitted destinations.
Practical questions
What should you decide upfront?
Are project settings fixed rules that cannot be changed?
They are defaults that the API can inherit. Authorised users can change the project, and an authorised API request can override processing settings. Project permissions and an API key’s restriction to a project remain separate access controls.
Does headless work with my own vault key?
The headless API route is available for server-managed workspaces. The current BYOK approach with your own vault key requires an unlocked browser and the app. Choose the setup that fits your key management and process.
Does anonimize send the result to another application itself?
Your own integration checks processing status, retrieves the output and sends it to the next step. In n8n, Power Automate and Zapier, you configure this with general HTTP or API actions.
How do I include human review?
Add an explicit review checkpoint to your workflow before passing the output on. Required export approval protects document downloads and key exports; processed JSON may already be available through the API. Configure your integration to continue only after your chosen release.
Which output can my workflow use?
Processed text is available as JSON. You can retrieve file results as a ZIP containing new TXT, PDF or DOCX documents; original formatting is not guaranteed. A reversal key, if any, is exported separately. Keep it apart from the output and include it only when deliberately needed.
From idea to integration
Where should anonimize fit in?
Tell us where your documents come from, who sets the rules and where the result needs to go. We can discuss the right route.