# Define Bridge

You can add external adapters to a Plugin node by creating a bridge in the Node Operators Interface. Each bridge must have a unique name and a URL for the external adapter. If a job has a Bridge Task, the node searches for a bridge by its name and uses that bridge as your external adapter. Remember, Bridge names are case-insensitive.

To create a bridge on the node, go to the **Create Bridge** tab in the Node Operators Interface. Specify a name for the bridge, and the URL for your external adapter, and optionally specify the minimum contract payment and number of confirmations for the bridge.&#x20;

![](/files/Ri4gUqN0SpjoKzy8cO3J)

**Bridge Name** - Must be unique to your plugin node and it is user-defined. For instance, if your external adapter brings your temperature value. Name it as "Temperature" so you can easily refer back to what the bridge does

**Bridge URL** - It should be the URL where the external adapter is running. Mostly try to set this up in your server where the Plugin node is running.

**Minimum Contract Payment** - This is a fee paid in PLI for the Plugin node making a call to the external adapter via the bridge. This fee is in addition to the fee specified at the global node level for processing job requests.

**Confirmation** - Can be kept as 0

***For example -***&#x20;

![](/files/PvIJc6MTWxUmecjzpeMv)

Note: If the external adapter is running on the same server as your plugin node. Keeping it as localhost.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.goplugin.co/external-adapters-plugin-1.0-deprecated/define-bridge.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
