Nobody should be moving files by hand.
IntELIEKonnect pulls documents out of the mailbox, drive or database they already live in, feeds them to the pipeline, and delivers the finished result to your systems, on a schedule, with a receipt for every send.
- Import & export connectors
- Pull & push scheduling
- Per-target receipts
What it does
Plumbing, done properly.
Collects from where the work already is
Mailboxes, drives, object storage and databases. Nobody has to change how they send you things for the pipeline to start.
Runs on a schedule you set
Pull on an interval or push on completion, with dedup so the same file arriving twice does not become two jobs.
Proves what left and when
Every delivery produces a per-target receipt. A failed target is reported as terminal rather than retried silently forever.
Use cases
Where teams point it first.
- 01
A shared mailbox fills up with attachments that someone downloads by hand each morning.
The mailbox becomes an import connector and the morning job disappears, along with the messages people forget to forward.
- 02
Finished results have to be re-uploaded into a line-of-business system.
Export targets receive the result directly, and the receipt is the evidence that it arrived.
- 03
The same document gets re-sent by two people on the same day.
Content hashing catches the re-send at ingestion, so it never costs a second run.
- 04
A downstream system is down and nobody notices until the end of the week.
Failed targets are surfaced against the job rather than buried in a log, and processing is never blocked by delivery.
How to use it
Four steps from manual to automatic.
- /import-connectors/create
Create an import connector
Pick the transport, give it credentials, point it at a folder or query. Test the connection before you trust it with a schedule.
- /$connectorId/schedule
Decide how often it runs
Pull on an interval, or let the source push. Priority lanes exist for the work that genuinely can't wait behind a nightly batch.
- bindings
Bind it to where the work happens
A binding says "files from this connector belong to that module's target". Konnect doesn't need to understand the target, which is why one connector can serve several products.
- /export-connectors · /export-settings
Add the exports, then watch the receipts
Configure where finished results go and in what format. Delivery runs on its own track, so a broken endpoint never re-opens a job that has already been processed and reviewed.
Works well with
intELIEdocs
The usual destination for what a connector collects, and the source of what it sends back.
ExploreaskKIRA
Keeps a knowledge base current from the systems your content already lives in.
ExploreVoice IntELIEgence
Delivers recordings in and pushes conversation scores back out on the same schedule.
ExplorePoint us at the folder nobody wants to open.
We'll wire a connector to it, run what is inside through the pipeline, and show you the delivery receipts on the other side.