> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/tips-and-tricks/how-to-add-embed-a-storylane-demo-in-a-zendesk-article.md).

# How to Add/Embed a Storylane Demo in a Zendesk Article

To embed a Storylane demo into your Zendesk article, follow these steps:

## **1. Enable iFrame Embeds in Zendesk**

Before embedding, ensure that Zendesk allows iFrame content:

1. Navigate to **Settings** > **Guide Settings** in your Zendesk dashboard.
2. Scroll down to the **Security** section.
3. Enable the **Display unsafe content** option to allow iFrames.

## **2. Obtain the Storylane Embed Code**

Retrieve the embed code for the Storylane demo you wish to include:

1. Log in to your Storylane account.
2. Navigate to the demo you want to embed.
3. Click on the **Share** > Embed > Inline
4. Copy the provided embed code.

## **3. Embed the Storylane Demo in Your Zendesk Article**

Now, insert the Storylane demo into your Zendesk article:

1. In Zendesk, go to **Guide** > **Manage Articles**.
2. Select the article where you want to embed the demo or create a new one.
3. In the article editor, click on the **Source Code** icon (`< >`).
4. Paste the Storylane inline embed code into the desired location within the HTML.
5. Click **Apply** to insert the code.
6. Save and publish your article.

By following these steps, you can enhance your Zendesk articles with interactive Storylane demos, providing a more engaging experience for your users.


---

# 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.storylane.io/tips-and-tricks/how-to-add-embed-a-storylane-demo-in-a-zendesk-article.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.