> For the complete documentation index, see [llms.txt](https://docs.plugin.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plugin.global/external-adapters-plugin-1.0-deprecated/define-bridge.md).

# 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. 

![](/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 -*** 

![](/files/PvIJc6MTWxUmecjzpeMv)

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