Skip to content

Creating a System

System setup in superglue is agent-first. Tell the agent which service you want to connect and what you need to do with it. The agent configures the connection and authentication, then asks for secret values through the secure credential flow when they are required.

  1. Describe the system: Name the API, database, file server, or internal service and the task you want to perform.
  2. Review the connection: The agent configures the endpoint, authentication method, and required secret names.
  3. Add credentials securely: Enter requested secret values in the credential form rather than in chat.
  4. Test access: The agent makes a safe test call and adjusts the configuration if needed.
  • A system is the reusable connection and authentication definition. It declares which secret names are required but does not contain each user’s account values.
  • A credential is a named set of secret values bound to one system.
  • A run uses a specifically selected credential or your default credential for that system.

One system can have multiple credentials for different users, service accounts, or customer accounts without duplicating the connection.

The agent identifies and configures the appropriate authentication method for you. superglue supports:

None

For public services or connections that handle authorization outside the request.

API keys and bearer tokens

The agent declares the required secret name and places the value in the appropriate header, query parameter, or request field at runtime.

Basic Auth

Credentials provide the username and password required for one account.

OAuth 2.0

superglue supports authorization-code and client-credentials flows, managed or custom OAuth clients, and automatic refresh for supported tokens.

Connection strings

For PostgreSQL, SQL Server, Redis, SFTP, SMB, ODBC, and custom protocols. Credentials provide account-specific values such as usernames and passwords.

After the system is saved, use its Authentication section to:

  • Create multiple named credentials for the same system.
  • Mark one credential as your default.
  • Share a credential with users or roles through access rules.
  • Rotate a secret value without changing the system or its tools.