> 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-multi-system-integration/3.-running-the-integration.md).
# 3. Running the Integration
In the previous two steps, we added the configuration information for our mock banking core, and set up a Service Request to map the received data from `randomuser.me` to the format expected by the mock banking core.
Now we can run the integration and see the new user created in the mock banking core.
First, open the [mock banking core](https://sandbox.demo-systems.sandboxbanking.com) and review the list of users present.
Sandbox Mock Core. Data may be different when you view the Mock Core.
Return to Integration Gateway, right click on our integration, and click *Run Integration.* Click *Execute* on the **Integration Runner**. Verify that the integration ran successfully. Check the output of the integration and remember the name of the new user.
{% hint style="danger" %}
If your integration resulted in a failure, double check the field mappings you created in the [previous step](/tutorials/building-a-multi-system-integration/2.-field-mapping.md). Verify that the values are entered exactly as instructed.
{% endhint %}
Now return to the [mock banking core](https://sandbox.demo-systems.sandboxbanking.com) and refresh the page. You will now see the new user that we received from `randomuser.me` as an entry in the mock banking core.
***
Congratulations! :raised\_hands: You've now built an integration that connects two different systems and bridges the gap in their data formats.
The process shown in this and the prior tutorial form the basis of building integrations in Integration Gateway. You can extend this model to build powerful transformations, processors, and connections between an ever-growing list of third-party systems.
---
# 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-multi-system-integration/3.-running-the-integration.md?ask=&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.
