Conduit

Connectors

Each connector pulls one endpoint into one SQL table on a schedule.

Type at least 3 characters and press Enter to search.

Producers

Register an API, set how it authenticates, then import or add its endpoints.

Type at least 3 characters and press Enter to search.

Activity

Step-by-step log of every run, newest first.

Type at least 3 characters in a text box and press Enter to search.

Customer

Clients you load data for. Each can write to its own destination database.

Type at least 3 characters and press Enter to search.

Users

Who can sign in, and what each of them may do.

Loading…

Dashboard

How your connectors are doing right now.

Loading…

Retention Settings

How much activity history to keep. Older entries are removed automatically.

Keep activity for
days
Entries older than this are deleted by a background sweep that runs hourly. Set 0 to keep everything and turn the clean-up off.
Stored now
—
Apply now runs the sweep immediately instead of waiting for the next hour.
Default SQL Server
A server-level connection whose login can see several databases. Customers can then pick a database by name instead of each having its own connection string.
—
Leave Database out of the string — each customer supplies its own. The password is stored on the server and is never sent back to this page, so leaving the box blank keeps it.
Local connector signing
Signs the local connector binaries, so Windows will run them without blocking or quarantining. Upload both: the public certificate ships inside every install package, and the key stays here. Leave empty if the connectors are unsigned, or signed by a publicly trusted authority.
—
Ships inside every install package so the target machine can trust the signature. Safe to distribute — it cannot sign anything.
—
Signing inside a web host is unreliable — a sandbox can stop signtool reading its own inputs. Instead, sign the binaries once on a machine with the Windows SDK and upload the result. They are identical for every connector, so this only repeats when the agent code changes.
Extract the download, double-click Sign-Binaries.cmd inside it, then upload the signed-binaries.zip it produces.
—
Single sign-on (Microsoft Entra)
Staff sign in through your directory, so your conditional access and MFA policies apply. Customer accounts keep their passwords and are unaffected. Accounts are never created automatically — a person must already have an active account here, matched on their Entra sign-in address.
In the app registration, under Authentication, add this exact value as a Web redirect URI. A mismatch here is the usual reason a first attempt fails.
The value of the secret, not its ID. Entra shows it once, when it is created.
Leave this on. If the directory is unreachable, or the app registration expires, it is the only way back in — including for whoever would turn SSO off.
Configure and save first, then use Test sign-in, then enable. Testing does not require this to be on and does not change your current session.
How data is written
Each write mode can use a different method. BulkCopy writes everything in one transaction — fast and all-or-nothing, so a failed load leaves the table untouched. Insert streams in batches as data arrives — lower memory, and each batch lands as it goes.
Replace empties the table then loads. BulkCopy keeps the old data if the load fails.
Append adds rows each run. Insert streams them as they arrive.
Applies to every connector, on its next run.

Setup

Name the console, set its logo, and pick the colours it uses.