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

![](https://1713380242-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl1AVRR4cLSYjVp62RmtY%2Fuploads%2F1JBgp8USDmvM1u12imqv%2Fimage.png?alt=media\&token=fba28b34-83f9-4edc-878e-649312c410ba)

**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 -*** 

![](https://1713380242-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl1AVRR4cLSYjVp62RmtY%2Fuploads%2FS44RdEblCrXRSSGwgExl%2Fimage.png?alt=media\&token=e44fa301-2880-496e-a270-1b959df0205a)

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