10 Processing Categories
After extraction, watchtheink routes field values through one of ten processing modes. Each maps to a distinct API layer — pick the categories your integration needs.
Entity Definition / Evolution
Create or update records in an external system from extracted field values.
Example: A registration scan creates a new contact in your CRM, or updates an existing one on re-submission.
Answer Validation
Compare extracted values against a known answer key and compute a score.
Example: Quiz answer sheets graded automatically — each field matched against the expected answer, score returned per field and total.
Data Entry into Existing Schema
Map extracted fields to columns in a database table with type coercion and constraint checking.
Example: An intake form populates a patient record table — dates parsed, required fields validated before write.
Aggregation over Multiple Scans
Collect values across many scans of the same template and compute statistics.
Example: Survey results aggregated into totals, averages, and distribution charts after a batch of 200 scans.
Delta / Diff Detection
Compare the current scan against a previous version to surface only what changed.
Example: A re-submitted amendment form — only modified fields are flagged for human review.
Multi-Source Aggregation
Combine data from scans of different templates into a single output record.
Example: A registration form and a consent form merged into one unified participant record.
Exception / Anomaly Detection
Flag scans where values fall outside expected ranges, confidence is low, or required fields are missing.
Example: A score of 150/100 triggers an exception record; a signature field below 60% confidence is held for review.
Workflow Triggering via External API
Use extracted values as inputs to a webhook or external API call when a condition is met.
Example: A checkbox marked "urgent" fires a POST to your support ticketing system with the scan data as payload.
Classification Without Predefined Schema
Ask the AI to classify and group fields semantically when no template is defined.
Example: Mixed incoming mail scanned and routed to Finance, HR, or Legal based on content — no pre-built template required.
Compliance Activity Logging
Append an immutable audit record for every scan: submitter, timestamp, template, and any post-extraction corrections.
Example: Every exam scan gets a signed log entry — who submitted it, when, and whether any field was manually corrected.
Ready to integrate?
See the API reference for endpoint schemas and authentication.