Binding an import connector to an orchestrator
Fetching is only half the job — a connector needs somewhere to put what it finds. You make that link from the orchestrator, in IntelieDocs: nothing in IntelieKonnect binds a connector.
- The IntelieKonnect module visible in your left-hand navigation.
- These permissions: IntelieKonnect — Update, IntelieKonnect — Delete.
- An import connector that is Active and Connected, plus the orchestrator you want to feed. Ineligible connectors are hidden from the picker rather than greyed out.
If IntelieKonnect isn't in your navigation, your role doesn't have visibility for it — ask a workspace administrator, or see Permissions and module visibility.
Steps
Select IntelieDocs in the side navigation, then open the orchestrator the documents should land in — a Smart Extract, Smart Classes, Smart Queue or Smart Redact.
In the orchestrator’s left rail, select Import Channels. The table lists the connectors already feeding it, under NAME, TYPE, STATUS and ACTION.
Open the dropdown on the right — it reads Import Channels Selected with a count — and use Search by name if the list is long. Tick the connector you want.
There is no Save step: the tick takes effect at once and the connector appears as a row. Its ACTION cell reads Disconnect, which means the channel is live.
Run Fetch now on the connector, then select Manage Documents in the orchestrator header to watch the documents arrive.
What success looks like
- The connector is a row in the Import Channels table with STATUS Active.
- Its ACTION cell offers Disconnect — the binding is enabled.
- Fetched documents appear in the orchestrator instead of going nowhere.
Removing or pausing a channel
Disconnect pauses a channel: the row stays and the button flips to Connect. The trash icon (Delete) removes the binding after a confirmation, and un-ticking the connector in the dropdown removes it instantly with none. Either way the connector keeps running its schedule — anything it fetches while the channel is removed or disconnected is consumed silently, never reaches the orchestrator, and is not fetched again afterwards.
If something goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| The connector is missing from the dropdown. | It is not both Active and Connected. Ineligible connectors are hidden, with no explanation in the tab. | Verify it, then enable it — see Verifying and Enable, disable, delete. |
| A SQL Database or MongoDB connector never appears. | Row-based connectors are Knowledge Base sources, not document channels. | Bind it under Knowledge Base instead. |
| No import channels found. | Nothing is bound to this orchestrator yet. | Add a connector from the dropdown. |
| The table is empty although you know a connector is bound. | Your permissions cover only the other direction. | Ask an administrator — see Permissions. |
| Couldn't load connectors. Please try again. | The connector list did not load. | Reload the page, then retry. |
Next
- Fetch now — prove the channel end to end.
- Schedules — let the connector run on its own.
- Connector statuses — the two badges eligibility depends on.