Connect Where YourDocuments Live.Deliver Results.
MiruIQ connectors define how documents enter pipelines and how files, extracted data, and validation results are delivered to downstream systems: the document processing integrations that wire MiruIQ into your existing stack.
Decouple Processing From Integration
Connectors separate document processing logic from system integration.
They allow pipelines to evolve without rewriting ingestion or delivery code, adapting to new sources and destinations as your infrastructure changes.
Input Connectors
Bring documents into pipelines from cloud storage, APIs, file servers, or external triggers. Connectors normalize ingestion so pipelines remain source-agnostic.
File Output
Route processed files to storage systems, forward them to downstream services, or archive them based on classification results and pipeline logic.
Data Output
Deliver structured extraction results directly to databases, analytics platforms, or APIs, enabling downstream automation without manual data handling.
Validation Output
Export detailed verification outcomes, field-level comparison results, and audit trails for compliance, reporting, or human-in-the-loop workflows.
Bring Documents Into the Pipeline
Input connectors deliver files into MiruIQ pipelines from any source system.
Regardless of the source system, documents enter the pipeline in a standardized form and can then be classified, extracted, verified, and routed.
Input connectors support asynchronous ingestion and can be triggered automatically or explicitly via API.
Object & File Storage
Connect to cloud storage systems and file servers for document ingestion.
Poll directories or buckets for new files, or receive event-driven notifications when documents arrive.
Supports batch ingestion, file filtering, and automatic cleanup after successful processing.
APIs & Services
Ingest documents via HTTP endpoints and webhooks.
Accept documents via direct file upload, base64-encoded payloads, or webhook triggers from external systems.
Ideal for integrating with existing applications, automation platforms, or custom workflows.
Cloud Drives
Connect to consumer and enterprise cloud storage.
Monitor shared folders for incoming documents and automatically ingest new files into pipelines.
Supports authentication via OAuth and service accounts for secure access.
Route, Store, or Forward Files
File output connectors control what happens to the original document file after processing.
They are typically used to store files long-term, route them based on classification or validation results, or forward them to downstream systems.
File routing is independent of data extraction: files and extracted data can be delivered to different destinations in parallel.
Object & File Storage
Store processed files in cloud storage or file servers.
Archive original documents, store annotated versions, or organize files into structured directory hierarchies based on classification results.
Supports configurable naming conventions, metadata tagging, and retention policies.
APIs & Services
Forward files to external services or automation agents.
Push documents to downstream systems via HTTP POST, trigger webhooks, or integrate with RPA platforms and document management systems.
Supports custom headers, authentication, and retry logic for reliable delivery.
Cloud Drives
Deliver files to consumer and enterprise cloud storage.
Automatically upload processed documents to cloud drives for easy access, sharing, and collaboration.
Organize files into folders based on document type, date, or custom classification results.
Deliver Extracted Data
Route extracted data from documents directly into databases, analytics platforms, or downstream applications.
Extraction output connectors deliver the structured data extracted from your documents (fields, tables, and values pulled from invoices, contracts, forms, and more) directly into your target systems.
Whether you need to populate a database, feed an analytics pipeline, or sync with an ERP, these connectors handle the delivery automatically using JDBC-based connectivity.
Relational Databases
Store document extracts in traditional SQL databases.
Insert extracted fields and tables from documents directly into your database schemas. Supports upsert operations, transaction management, and flexible schema mapping.
Perfect for integrating document data with ERP systems, data warehouses, and operational databases.
Cloud & Managed Databases
Deliver document extracts to cloud-hosted databases.
Route extracted data from documents to cloud-native databases with built-in connection pooling, SSL encryption, and automatic failover support.
Compatible with serverless configurations and managed database offerings from major cloud providers.
Analytics & Query Engines
Feed document extracts into analytics platforms.
Stream data extracted from documents into analytics systems for real-time dashboards, reporting, and business intelligence workflows.
Supports batch and streaming modes with configurable partitioning and data formats.
Deliver Decisions, Not Just Pass/Fail
Validation modules produce explicit, structured verification results in addition to controlling pipeline flow.
These results describe what was checked, what matched, and what failed, across individual documents or entire document groups, and can be delivered just like extracted data.
This enables auditable decisions, downstream automation, and human-in-the-loop workflows.
Validation Output Capabilities
Structured verification results that go beyond simple pass/fail status.
Each validation result includes the original extracted value, the reference value, the comparison outcome, and any normalization applied during matching.
Results can be aggregated at the document or group level, enabling downstream systems to act on overall verification status rather than individual field outcomes.
Output Delivery
Validation results use the same output connectors as extraction results.
Route verification outcomes to databases, analytics platforms, or APIs for auditing, compliance reporting, or triggering downstream workflows.
Failed validations can be automatically escalated to human review queues or exception handling systems.
Extend When Needed
If a required source or destination is not yet supported, MiruIQ can implement custom connectors for customer-specific systems.
This ensures pipelines remain adaptable even in complex or proprietary environments.
Seamless Integration
Integrate seamlessly with existing pipelines
Same Security Model
Use the same execution and security model
Fast Delivery
Typically delivered within 1–2 days
Fully Adaptable
Works with complex or proprietary environments
Integration Questions
The document processing integrations teams ask about most.
S3 and S3-compatible object storage, SFTP, email inboxes, Google Drive and HTTP APIs. Documents enter the pipeline the moment they arrive at the source: no manual uploads, no polling scripts.
As structured JSON per document, via webhooks, direct database inserts, S3 buckets or HTTP push to any ERP or DMS, delivered the moment verification completes.
No. Connectors are configured directly in the pipeline builder with encrypted credentials; a pipeline typically goes from configuration to production without custom integration code.
Seamless Integration Zero Friction
Connect MiruIQ to your existing systems, without custom code or middleware.