Client systems

Every implementation touches at least two systems: the one the client is leaving and the one they are moving to. superglue connects both the same way. You describe the system to the agent, it configures the connection from the vendor’s documentation, and you enter the secret values in a secure form. There is no connector library to be limited by.

Connect a system

1. Start a session and name the system and what you need from it, for example “Connect the client’s Sage Intacct sandbox so we can load vendors.”
2. The agent configures the endpoint and the authentication method. For common ERPs such as Sage Intacct, NetSuite, Dynamics 365 Business Central, Acumatica, QuickBooks, Xero and SAP, it starts from a built-in template with documentation already loaded.
3. Enter the requested secret values in the credential form. Never paste them into chat.
4. The agent makes a safe read to confirm access.

You can also start from Capabilities → Systems and select Add System. For the details of authentication types, see Creating a system.

!

One system, many clients. A system stores the connection definition. Each client’s login is a separate named credential on that system, so your Sage Intacct system serves every Intacct engagement without being reconfigured.

Legacy sources

Legacy systems rarely have a clean API. superglue handles the usual cases:

• Direct database access: SQL Server, PostgreSQL, ODBC and other databases connect as systems. The agent queries tables directly, so a Dynamics GP or Sage 100 database is a normal source.
• File exports: When the client can only send extracts, upload the Excel, CSV or XML files. See Project context. Uploaded files are parsed and become a source the agent can profile and map like any other.
• File servers: SFTP and Windows file shares connect as systems, which suits clients who drop exports on a server on a schedule.
• Legacy applications with no interface: Some products expose only a local automation interface. The secure gateway can run scripts on a Windows host inside the client’s network for these cases.

On-premise and private networks

Many legacy systems are reachable only from inside the client’s network. The superglue Secure Gateway is a small process the client’s IT runs on a machine in that network. It opens an outbound encrypted connection to superglue and exposes only the targets listed in its configuration. No inbound firewall rules are needed.

Once the gateway is connected, you create a Private System that points at one of its targets, and it behaves like any other system. See Connecting to on-prem systems for the setup you can hand to the client’s IT team.

The target system

Connect the target with a sandbox or test company first. The agent uses it to verify mappings and to load sample batches before anything touches production. When the client signs off, add the production credential to the same system. Tools do not change; only the credential selected for the run does.

!

Keep test and production credentials clearly named, for example “Contoso sandbox” and “Contoso production”. The credential a run uses is shown in the run record, so the trail stays clear.

Client IP allowlisting

Some clients restrict API access by source IP. superglue Cloud uses fixed outbound addresses listed under Cloud networking. Self-hosted deployments use their own.