> 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-an-event-driven-integration/3.-triggering-the-integration-from-the-crm.md). # 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 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-an-event-driven-integration/3.-triggering-the-integration-from-the-crm.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.