Shared folder
A local or network folder on the engine's machine - the simplest way to take files from a lab system.
Files↓ Inbound↑ OutboundFOLDERcamel-fileThe path is read by the engine, so it must exist there (or be a share the engine can reach), with read permission for inbound or write permission for outbound.
Leaving Move processed files to blank keeps processed files in a .done folder beside them.
Worked example
Demo order folder · Inbound · CSV · Test passes on any engine: Yes
The engine's own temporary folder, so Test passes anywhere. Use the lab's drop folder for real.
{
"direction": "Inbound",
"format": "CSV",
"settings": {
"path": "<engine temp folder>",
"filePattern": "*.csv",
"pollSeconds": "30"
}
}
This is what the console's Fill example button enters. Secrets are never part of an example. Every setting is explained below.
Settings
Required fields are marked Yes. This connector has no secret fields. A field marked inbound only or outbound only appears just for that direction.
| Setting | Type | Required | Default | What to enter |
|---|---|---|---|---|
pathFolder | text | Yes | — | Required: the folder on the engine's machine or a share, e.g. D:\lab\incoming or \server\share\orders. |
filePatternFile name pattern | text | No | *.csv | inbound only. Which files to pick up, e.g. .hl7 or ORM_.hl7. Others are left alone. |
archivePathMove processed files to | text | No | — | inbound only. Blank keeps them in a .done folder beside them. |
pollSecondsPoll every (seconds) | number | No | 30 | inbound only. How often to look for new files, e.g. 30 (seconds). |
What "Test connection" checks
The folder exists and the engine can read it (inbound) or write to it (outbound). No file is created.
Test connection is read-only and says how far it got: verified, reached, checked or failed. See Testing a connection, and Troubleshooting if it fails.