> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superglue.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# superglue for non-coders

> From first login to a working tool.

superglue builds the connection between your systems. You tell it which connection you need in plain English, and it builds the integration and manages it for you.

<Card title="Log in to superglue" icon="arrow-up-right-from-square" href="https://app.superglue.cloud" horizontal>
  Log in at app.superglue.cloud, or use your organization's private URL if superglue is self-hosted.
</Card>

The easiest way to get started with superglue is to talk to it. In case you still want an overview, here is a guide.

## Good to know

<CardGroup cols={2}>
  <Card title="System">
    The data source you connect to, for example BigQuery, Salesforce, Business Central, or SAP.
  </Card>

  <Card title="Tool">
    The connection itself. A tool performs one action against a system: read records, push data, run a report.
  </Card>

  <Card title="MCP server">
    Enables you to use tools you built in superglue in environments like Langdock or Claude Code, or share them with colleagues.
  </Card>

  <Card title="Credentials">
    Your personal access keys for a system. You always add your own, they are encrypted, and no AI sees them.
  </Card>
</CardGroup>

## Find your way around

Six places you will use:

* **Agent.** Where you spend most of your time. Ask it to build an integration or discover a system in plain language.
* **Tools.** Your built connections and automations.
* **Systems.** Which systems are connected to superglue. You can use a system, as soon as you have added your credentials.
* **Credentials.** Your personal keys per system. You only see data you have credentials for. Here, you also can add your credentials.
* **Runs and Control Panel.** Run history.
* **MCP Servers in the Control Panel.** Build, manage, and export your MCP servers.

## Create a tool

<Steps>
  <Step title="Open a new chat in the agent">
    The superglue landing page. To open a new chat, use the top right of the screen.
  </Step>

  <Step title="Describe what you want in plain language">
    For example: "I want to have my data from Salesforce in BigQuery." Vague is fine; the agent asks back for whatever it needs.
  </Step>

  <Step title="Let the agent connect the source system">
    The agent asks permission and guides you through setup, so it can read the field names itself instead of guessing.
  </Step>

  <Step title="Choose how it runs">
    The agent offers options like real-time or on a schedule. Pick what suits the use case.
  </Step>

  <Step title="Iterate, then save the tool">
    The superglue agent inspects and tests each step, and confirms it with you. If you hit a wall in building a tool, ask in the chat how to proceed.
  </Step>
</Steps>

<iframe className="w-full aspect-video rounded-xl" src="https://drive.google.com/file/d/1nX5AatG_MLiKDqxQgg-B4wkzGRg-XpC9/preview" title="Build a tool in superglue" allow="autoplay" allowFullScreen />

## Add your credentials

A tool can only pull data once you give superglue access to the system. How that works depends on the system:

* **API key.** A pop-up opens, you paste the key, and it is encrypted. AI never touches it.
* **OAuth or SSO.** A login window opens (for example Salesforce). You log in there and superglue connects without ever holding a key.
* **Basic auth.** You enter a username and password, both encrypted at rest.
* **Connection string.** For databases like Postgres or MSSQL, you paste a connection string.

**Credentials are personal.** If a colleague shares a tool with you, you still need your own credentials to pull any data. You can only reach systems you already have access to; superglue cannot open a door that is locked for you.

<iframe className="w-full aspect-video rounded-xl" src="https://drive.google.com/file/d/1Jz_JHQ6jnvMX4vot8GlYUQ1x9ZZd8sJA/preview" title="Adding credentials" allow="autoplay" allowFullScreen />

## Use a superglue tool in environments like Langdock

<Steps>
  <Step title="Build an MCP server">
    In the Control Panel, hit the plus, name the server, and add the tools you created. You can also ask the agent to create the MCP server for you in the chat.
  </Step>

  <Step title="Export it for Langdock">
    One click. Langdock and Claude Code use slightly different file formats, so pick the Langdock export. You get a file to import.
  </Step>

  <Step title="Import it in Langdock">
    Go to Integrations, then Add Integration, choose the file you exported, and import it.
  </Step>

  <Step title="Configure and add the connection">
    The tools from the MCP server appear automatically. Select the ones you need and add them.
  </Step>

  <Step title="Call the tools in chat">
    Ask your questions in plain language in Langdock and the tools run for you. No clicking around the source system.
  </Step>
</Steps>

<iframe className="w-full aspect-video rounded-xl" src="https://drive.google.com/file/d/1zIEoeurvTb-DUrDyKz3x-n9JFTyZ317J/preview" title="superglue in Langdock" allow="autoplay" allowFullScreen />

## Security and data

* **AI builds.** AI is used only to build the connection. Once built, the connection runs as a fixed, deterministic process, like one built by a developer.
* **No data leaves your organization.** Your data is only accessible to the people you give access to.
* **Self-hosted means self-contained.** If you self-host superglue, it runs on your servers and nothing leaves your systems.
* **Permissions still apply.** Existing permission sets carry over. You cannot reach data you do not have credentials for.

***

<Tip>
  The easiest way to find out if superglue can help with your work is to just ask it in the chat.
</Tip>