Connectors
Connectors move documents in and out of DocAI Fabric automatically, without anyone clicking Upload. You configure a connector once, and from then on documents flow into your project on their own.
Import connectors
Import connectors watch an external source and pull new documents into a project. Each new file becomes a transaction that runs through your normal workflow (Import, OCR, Split, Classify, Extract, and so on), exactly as if the file had been uploaded by hand or through the API.
| Connector | Source | Status |
|---|---|---|
| Import from Hotfolder | A watched folder on a filesystem the deployment can see (local disk, NFS or SMB share, Azure Files) | Available |
| Import from Email | A mailbox folder: any IMAP server, or Microsoft 365 via a Graph app registration. One email = one transaction (body as PDF + attachments) | Available |
| Cloud storage | Your own Azure Blob Storage, Amazon S3, or Google Cloud Storage container | Planned |
| Inbound email address | A dedicated receive-only address hosted by DocAI Fabric | Planned |
| SFTP | Your own SFTP server | Planned |
Availability by deployment
What a connector can reach depends on where DocAI Fabric runs:
| Deployment | Hotfolder | Cloud storage (planned) | |
|---|---|---|---|
| Self-hosted (on-premises, Docker) | Yes, available by default | Yes, with your mailbox credentials | Yes, with your credentials |
| Managed in Azure (your subscription) | Yes, enabled on request as a deployment setting | Yes, with your mailbox credentials | Yes, with your credentials |
| SaaS (app.docaifabric.com) | No (the platform cannot expose a shared filesystem) | Yes, with your mailbox credentials | Yes, with your credentials |
Export connectors
Export connectors push processed results out of DocAI Fabric (for example into a database or an ERP system). Today, results leave the platform through the Export activity and webhooks; richer export connectors are planned on the same framework.