> 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/2.-calling-the-external-system.md).

# 2. Calling the External System

**Create the Service Request**

{% hint style="success" %}
A new feature called [**Buildhelper**](/integration-gateway-platform-reference/buildhelper.md) is now available to help creating new Service Requests for various external Systems / APIs with pre-created fields for various request types.
{% endhint %}

Now that the integration has been created, we can begin to add logic to it. For this tutorial, we will simply call the `randomuser` API and receive its response.

Right click on the integration, click *Go To*, then click *Service Request*.

<figure><img src="/files/vxLIwsK92dNBm9FwDFuG" alt=""><figcaption><p>Right click > Go To > Service Request</p></figcaption></figure>

You will see an empty table.

On the toolbar along the bottom of the screen, click the plus icon (+) to add a new Service Request. This will create a new row in the table, which will be highlighted in green to indicate it was newly created.

<figure><img src="/files/scp6NmNr62tcYRq3TbsT" alt=""><figcaption><p>Newly created, empty Service Request</p></figcaption></figure>

We need to fill out three columns on this service request. You may need to scroll your screen to the right to see all of them.

| Column           | Value           |
| ---------------- | --------------- |
| System           | `HTTP`          |
| Service Name     | `n/a`           |
| Formula Variable | `request_users` |

Save your changes by clicking the *Save* icon on the bottom toolbar.

<figure><img src="/files/8Sy3ai9ADPYPfCIL6UdA" alt=""><figcaption><p>Filled out Service Request</p></figcaption></figure>

Next, we will create the Field Mappings for this Service Request.

**Create the Field Mappings**

Right click along the service request's row, then click *Go To*, then click *Field Mapping*. You will see an empty table.

{% hint style="info" %}
You can verify that you're on the correct page by checking the *Component* dropdown on the top-left of the page. At this step, it should read "Field Mapping".\
\
![](/files/VLdncHoQ8xa2ANqiqxUJ)
{% endhint %}

Create two new field mappings by clicking the plus icon (+) on the bottom toolbar twice. Fill out the first field mapping by entering the following values in the first row:

| Column     | Value    |
| ---------- | -------- |
| Field      | `method` |
| Value      | `"GET"`  |
| Value Type | `str`    |

Then, fill out the second field mapping with the following values:

| Column     | Value               |
| ---------- | ------------------- |
| Field      | `url_path`          |
| Value      | `"/api/randomuser"` |
| Value Type | `str`               |

<figure><img src="/files/eIK7yvhi1dy6Z1IZYYQK" alt=""><figcaption><p>Two field mappings, <code>method</code> and <code>url_path</code></p></figcaption></figure>

Save your changes.


---

# 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 dynamically by asking a question.

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

```
GET https://glyue.docs.sandboxbanking.com/tutorials/building-a-single-step-integration/2.-calling-the-external-system.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
