# 3. Triggering the Integration from the CRM

Return to the CRM.

Open the [mock core](https://sandbox.demo-systems.sandboxbanking.com) and familiarize yourself with its current contents. After running the integration, you will see the customer you entered in the CRM appear in the mock core.

Once both systems are open, return to the CRM and click *Send to Core*.

Return to the mock core and verify that the new customer was created in the core.

{% hint style="info" %}
For simplicity, this integration always creates a new user in the core when run. If you run the integration multiple times with the same input from the CRM, you will see duplicate entires in the mock core.
{% endhint %}

***

Congratulations! :tada: You have transformed your trigger-based integration into an event-based integration, and demonstrated connectivity between a mock CRM and mock banking core.

Over the course of these three tutorials, you have learned to leverage the simple but powerful framework at the heart of Integration Gateway: transforming data using field mappings and connecting systems using service requests. Using the knowledge you learned here, you can now create integrations tailored to your specific systems and needs.

As you grow into more complex integrations, we encourage you to make use of the extensive selection of How-To Guides and Reference Documentation to leverage the full power of Integration Gateway.

Happy building!


---

# 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://glyue.docs.sandboxbanking.com/tutorials/building-an-event-driven-integration/3.-triggering-the-integration-from-the-crm.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.