# Connection

## Integration User

Before we configure our Connection, we need to ensure we have a user in the instance to use as the Inbound user for our Integration. To configure our Integration user:

In the **native ServiceNow** window, navigate to **User Administration > Users**. Click **New**.

The fields to be configured for the User record are as follows:

|  #  | Field      | Description                                                                | Value                     |
| :-: | ---------- | -------------------------------------------------------------------------- | ------------------------- |
|  1  | User ID    | The id of the user (to be used by the external system for authentication). | \<your.integration\_user> |
|  2  | First name | The integration user's first name.                                         | \<Your First Name>        |
|  3  | Last name  | The integration user's last name.                                          | \<Your Last Name>         |
|  4  | Password   | The user's password (to be used in basic authentication).                  | \<Your Password>          |
|  5  | Roles      | The role required for access to the integrated records.                    | 'itil'                    |

*Your User record should look like this:*

![](/files/-MR-FkAf56F3eA7ARF3Q)

## Connection

{% hint style="info" %}
You can set up many connections to enable switching between environments (one connection per environment). However, only one connection can be active for an Integration at a time.
{% endhint %}

{% hint style="warning" %}
**Remember**: When setting up a Connection:

* Make sure your SOAP and/or REST endpoints are unique.
* Never use your own User as the Inbound User as it will prevent the integration from working.
* Always ensure that your Inbound User is NOT used by anyone else for the same Process i.e. if you’re creating a Connection for an Integration on the Incident Process, your Inbound User has to be the only User used by an Integration within that Process.
  {% endhint %}

{% hint style="success" %}
We are going to configure a Connection for the Development environment.
{% endhint %}

Back in the **Unifi Integration Designer** window, click on the **'Connections' icon**, then click **New**.

The fields to be configured for the New Connection modal are as follows:

|  #  | Field        | Description                                        | Value                           |
| :-: | ------------ | -------------------------------------------------- | ------------------------------- |
|  6  | Environment  | The environment this connection applies to.        | 'Development'                   |
|  7  | Endpoint URL | The external system's access URL.                  | \<External system Endpoint URL> |
|  8  | Active       | Use this connection for the integration when true. | \<true>                         |

## Outbound Connectivity

The format of the Endpoint URL is as follows:&#x20;

`https://<your_instance>.service-now.com/<your_resource_path>`

*Your New Connection modal should look like this:*

![](/files/-MR-Gwm-Eq9TWvrUYf07)

9\) Click **Submit and view**.

{% hint style="info" %}
Clicking 'Submit' will redirect you to the list view of the record you're creating. Clicking 'Submit and view' will redirect you to the newly created record.
{% endhint %}

## Connection Details

The fields to be configured for the Details form are as follows:

|  #  | Field          | Description                                                                                                                      | Value                            |
| :-: | -------------- | -------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- |
|  10 | Authentication | The authentication method to use for this connection.                                                                            | 'Basic'                          |
|  11 | User           | The username used in basic authentication.                                                                                       | \<external.system.user>          |
|  12 | Password       | The password used in basic authentication.                                                                                       | \<External system user password> |
|  13 | Inbound user   | The user profile used by the external system for authentication. An active connection must be found for the user to gain access. | \<lookup: Your Inbound User>     |

*Your Details form should look like this:*

![](/files/-MR-Hg31aqfuugf2aXee)

{% hint style="success" %}
**Feature Alert**: The widget at the bottom of the page now shows the Integration as Active.
{% endhint %}

{% hint style="info" %}
For this Development environment Connection, we have set the Endpoint URL to point to our own instance and used the same Integration User for both Inbound and Outbound *(as created above)*. Being able to connect to our own instance makes it simple and efficient to test our integration *(seeing Transactions going out and coming in)* before we connect to the external system.
{% endhint %}

14\) **Save** the Connection.

We are now ready to step back into the **native ServiceNow** window to configure the **Trigger**.


---

# 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.sharelogic.com/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/connection.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.