Document gateway quick menu
FormKiQ Document Gateways provide structured, ready-made configuration for connecting external document sources to the FormKiQ platform. Rather than building custom ingestion pipelines from scratch, Document Gateways give your implementation team a tested, documented starting point for each source system, standardizing how documents arrive in FormKiQ with their metadata, classification, and governance context intact.
Document Gateways are a distinct layer from FormKiQ's Capability Extension Modules. Where modules extend what FormKiQ can do with documents once they are in the platform, Gateways define how documents get there in the first place. They are available for FormKiQ Advanced and FormKiQ Enterprise deployments and can be deployed individually or in combination depending on where your documents currently live.
What Document Gateways provide
Document Gateways are not generic file sync connectors. Each gateway is designed around the specific document model, permission structure, and event patterns of the source system, with ready-made ingestion configuration, metadata mapping, and additional API endpoints where the standard FormKiQ surface needs to be extended to support source-specific interactions.
This includes:
- Structured ingestion from external document sources with metadata preservation and classification on arrival
- Permission and access model mapping, translating source system access controls into FormKiQ's RBAC and ABAC policies where appropriate
- Event-driven ingestion patterns triggered by document creation, modification, and movement in the source system
- Deduplication and reconciliation controls to ensure documents arrive in FormKiQ cleanly, without duplication or version conflicts
- Audit-safe ingestion records so every document's origin, ingestion timestamp, and source metadata are traceable within FormKiQ's audit model
- Configurable routing so incoming documents are classified, tagged, and directed to the appropriate workspace, site, or workflow on arrival
Google Drive and Google Workspace Gateway
Connect FormKiQ to Google Drive and Google Workspace to capture documents from Google's ecosystem into FormKiQ's governed environment. For organizations using Google Workspace for collaboration and document production, the Google Drive Gateway provides structured ingestion that brings documents into FormKiQ with their metadata, ownership, and version history preserved.
The gateway supports ingestion from shared drives and individual Drive locations, metadata mapping between Google Drive file attributes and FormKiQ document attributes, and event-driven ingestion triggered by document creation, sharing, and modification events in Google Workspace. Native Google formats — Docs, Sheets, Slides — can be converted to standard formats on ingestion, ensuring they are accessible within FormKiQ's document model without dependency on Google's rendering environment.
Common fits: organizations using Google Workspace as their primary productivity environment who need governed document management applied to specific document categories, teams producing documents in Google Workspace that need to enter a formal records or compliance workflow, and hybrid environments where Google Workspace and FormKiQ operate alongside each other with defined handoff points.
Email Ingestion Gateway
Capture documents arriving by email directly into FormKiQ, with structured ingestion of attachments, metadata extraction from message headers and body content, and routing to the appropriate workspace or workflow based on configurable rules.
The Email Ingestion Gateway is particularly valuable for organizations where documents arrive from external parties by email as part of defined business processes — applications, submissions, contracts, invoices, and other document types that need to enter a governed workflow immediately on receipt. Rather than relying on manual download and upload processes, the gateway captures incoming documents automatically and routes them into FormKiQ with classification and metadata applied at the point of ingestion.
Common fits: grants and applications intake, accounts payable document capture, contract and correspondence intake, insurance submissions, and any workflow where external parties submit documents by email as part of a defined process.
Secure File Transfer Gateway
Connect FormKiQ to SFTP and managed file transfer environments to capture documents arriving through secure transfer protocols. For organizations that receive documents from partners, government agencies, or regulated counterparties through SFTP or similar transfer mechanisms, the Secure File Transfer Gateway provides structured ingestion that applies FormKiQ's classification, metadata, and governance model to documents as they arrive.
The gateway supports scheduled and event-driven ingestion from SFTP locations, metadata extraction from file naming conventions and transfer manifests, and routing to appropriate workspaces and workflows based on source, file type, and configurable rules.
Common fits: financial services document exchange with regulators and counterparties, healthcare data and document exchange with payer and provider networks, government and public sector document intake from external agencies, and any environment where documents arrive through managed transfer protocols rather than user-initiated upload.
Document Scanner and Capture Gateway
Connect FormKiQ to physical document capture workflows — scanner systems, multifunction devices, and capture platforms — to bring digitized documents into FormKiQ's governed environment with OCR processing, metadata extraction, and classification applied at the point of capture.
The Document Scanner Gateway works in conjunction with FormKiQ's AI Processing and Analysis module to ensure that captured documents arrive in FormKiQ as fully processed, searchable, and attributed records rather than raw image files requiring manual classification. For organizations with significant paper document volumes or ongoing physical intake requirements, this gateway provides the connection between physical capture infrastructure and FormKiQ's digital governance model.
Common fits: records digitization programs, physical mail and correspondence intake, healthcare and insurance document capture, legal and government document intake, and any environment where physical documents need to enter a governed digital workflow.
Cloud Storage Gateway
Connect FormKiQ to cloud object storage environments — including Azure Blob Storage, Google Cloud Storage, and similar platforms — to ingest documents stored in unstructured cloud storage into FormKiQ's governed document layer. For organizations that have accumulated documents in cloud storage without a formal governance model, the Cloud Storage Gateway provides structured ingestion that applies metadata, classification, retention, and access control to existing document collections.
The gateway supports both bulk historical ingestion for migration programs and ongoing event-driven ingestion for environments where documents continue to be deposited into cloud storage as part of existing workflows.
Common fits: cloud storage migration and governance programs, organizations inheriting document collections from acquired businesses or discontinued systems, and environments where documents are produced by automated processes and deposited into cloud storage before entering a governed workflow.
Planning your gateway strategy
Document Gateways are most commonly deployed as part of FormKiQ Advanced and FormKiQ Enterprise programs, where document connectivity, migration, and governance requirements span multiple source systems. For organizations planning a migration from a legacy ECM platform or consolidating documents from multiple source systems into FormKiQ, a gateway strategy is typically one of the first planning conversations.
Gateways work alongside FormKiQ's Capability Extension Modules and Integration Frameworks. Where Integration Frameworks define how FormKiQ connects to enterprise systems of record and Modules extend platform capability, Document Gateways define how documents from external sources and collaboration environments enter the governed document layer. In many deployments, all three are in use together, each playing a distinct role in the overall architecture.
For organizations with source systems not covered by a standard gateway, FormKiQ's API-first architecture supports custom gateway development using the same ingestion and metadata patterns as the standard gateways.
Talk to FormKiQ About Document Gateways
Learn About FormKiQ Advanced · Learn About FormKiQ Enterprise · Review Integration Frameworks · Explore Modules