> For the complete documentation index, see [llms.txt](https://glyue.docs.sandboxbanking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glyue.docs.sandboxbanking.com/tutorials/building-a-single-step-integration/3.-running-the-integration.md).

# 3. Running the Integration

**Run the Integration**

Now we have finished building our integration and we are ready to run it and see the results.

Return to the "Integration" level of the **Build page** by using the *Component* dropdown in the top-left corner. Right-click on the integration we just made, and click *Run Integration*. This will open the **Integration Runner*****.***

<figure><img src="https://688288018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1flQ2To8tQpCQWl2Ty9U%2Fuploads%2FO7Y7HOYLKH8RC02BD5hQ%2FScreenshot%202024-09-03%20at%2012.09.32%E2%80%AFPM.png?alt=media&amp;token=c5e2528a-f528-4707-9654-42384be1e7bd" alt=""><figcaption><p>The Integration Runner</p></figcaption></figure>

The **Integration Runner** has many options for customizing the input to an integration, which can be useful when mimicking the request from an external system. For now, we will leave all the fields empty.

Run the integration by clicking the *Execute* button on the bottom-left.

You should see a green success message in the bottom-right of your screen.

{% hint style="warning" %}
If you receive an error, double check that the field mappings in [step 2](/tutorials/building-a-single-step-integration/2.-calling-the-external-system.md) were entered correctly.
{% endhint %}

**View the Results**

To view the results of our integration run, navigate to the **Run History** page using the navigation sidebar along the left.

You should see an entry in the left-side column corresponding to the name of the integration we just built. Open it by clicking on it, then click on the *Step* labeled "REQUEST".

<figure><img src="https://688288018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1flQ2To8tQpCQWl2Ty9U%2Fuploads%2Ft1PP17AkPRBqb1RxKwDl%2FScreenshot%202024-09-03%20at%2012.10.10%E2%80%AFPM.png?alt=media&amp;token=6d1195d2-74a0-44bd-b2f8-6366dcdcce7a" alt=""><figcaption><p>Run details for the integration</p></figcaption></figure>

In the detail pane on the right side, you will see two sections:

* `Request`, which reflects the values of the field mappings we created in step 2
* `Response`, which contains the response sent back to us by `randomuser.me`

Verify that the response object in the `payload` contains fields that relate to a person. Take note of the structure, specifically that the payload contains a field named `results`, which contains a list of objects, each representing a person. It should resemble the example below:

```
{
    "success": true,
    "payload": {
        "results": [
            {
                "gender": "female",
                "name": {
                    "title": "Miss",
                    "first": "Marte",
                    "last": "Hanssen"
                },
                "location": {
                    "street": {
                        "number": 3519,
                        "name": "Trasoppveien"
                    },
                    "city": "Kyrkstera",
                    "state": "Trndelag",
                    "country": "Norway",
                    "postcode": "5590",
                    
                },
                "email": "marte.hanssen@example.com",
                "dob": {
                    "date": "1948-03-02T07:02:33.244Z",
                    "age": 76
                },
                "registered": {
                    "date": "2002-11-07T07:03:35.787Z",
                    "age": 21
                },
                "phone": "56531940",
                "cell": "41662594",
                "id": {
                    "name": "FN",
                    "value": "02034819494"
                },
            }
        ]
}
```

Finally, click on the step labeled `OUTPUT`. Notice that it currently contains a generic message noting the integration completed successfully.

<figure><img src="https://688288018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1flQ2To8tQpCQWl2Ty9U%2Fuploads%2F5AnfeSi14rDpTAzvJGgl%2FScreenshot%202024-09-03%20at%2012.15.21%E2%80%AFPM.png?alt=media&amp;token=1d3538fa-5be6-48f3-9d5e-406ba64cbd93" alt=""><figcaption><p>The generic success message in the Output</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://glyue.docs.sandboxbanking.com/tutorials/building-a-single-step-integration/3.-running-the-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.