> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/kb/sdk-demo/integration-templates.md).

# SDK Demo: Integration templates

As you already know, the SDK Demo helps you get some hints on how to embed Appmixer into your product, and preview your configuration – in an imaginary SaaS platform – to see what Appmixer will look like once it lives inside your real platform.

The second SDK Demo we offer relates to the simplistic version of the integration builder. Say your end-users are not tech-savvy enough and want to integrate different apps as easily as possible. Impossible as it may seem, we've built a tool called Integration templates that does exactly that.

[In one of the previous sections, we showed you how to create integration templates using our drag\&drop visual designer](/kb/appmixer-studio-features/creating-an-integration-template.md). Now, it's the right time to preview your configuration and see what Appmixer will look like once it lives inside your platform.

Moreover, make sure to study the source code of the SDK demo to understand how to use the JavaScript SDK to display any of the Appmixer UIs in your product and to connect your users with the Appmixer virtual users to keep user data separate.

![SDK Demo: Integration templates preview](https://660555879-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Meyy9fJyhzsrd3q4-5N%2F-MhmU9CJyB11thl0hH7w%2F-MhmVd6iVrxO5GimgbK3%2Fpic-email-2-2.png?alt=media\&token=19373cd9-e06e-44cd-89ec-e186921633c6)

### How to access your SDK Demo?

For those of you who recently started a free trial, refer to one of the onboarding emails. We've generated a special link that will help you download the SDK Demo: Integration templates. Alternatively, you can download the SDK Demo below:

{% file src="/files/URZsmmppLiCEpLqQFCLq" %}


---

# 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://docs.appmixer.com/kb/sdk-demo/integration-templates.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.