> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/developer/embedded-iframes.md).

# Embedded Iframes

Pylon provides an out-of-the-box customizable iframe app that allows embedding of webpages within the issues and accounts view.

## Setup

1. Go to **Settings > Integrations & dev > Integrations** and open the **Iframe** app.
2. Click **Add iframe** and choose a **Display location**: **Issue sidebar** or **Account overview**. Account overview requires Account Intelligence.
3. Enter a **Title** and the **URL**. Type `{` in the URL field to insert variables (see below).
4. Optionally, add a **Description**, an **Icon URL**, and a **Height (in pixels, optional)**. The default height is 200 pixels.
5. Click **Save**.

Each iframe has its own title, icon, and height, and its own on/off toggle on the Iframe app page, so you can turn one off without deleting it. You can also reopen an account overview iframe's settings from an account notebook. Changes apply everywhere that iframe is used.

## URL variables

Use `{{ variable }}` in the URL to pass details about the issue or account you're viewing, for example:

```
https://metabase.example.com/dashboard/12?account={{account.id}}&viewer={{actor.email}}
```

### Issue sidebar

| Variable                                                                                                   | Value                                   |
| ---------------------------------------------------------------------------------------------------------- | --------------------------------------- |
| `issue.id`, `issue.number`, `issue.title`, `issue.body`                                                    | The issue's ID, number, title, and body |
| `issue.link`                                                                                               | Link to the issue in Pylon              |
| `issue.status`, `issue.source`                                                                             | The issue's status and source           |
| `issue.account.id`, `issue.account.name`, `issue.account.crm_account_id`                                   | The issue's account                     |
| `issue.requester.name`, `issue.requester.first_name`, `issue.requester.last_name`, `issue.requester.email` | The issue's requester                   |
| `issue.assignee.name`, `issue.assignee.first_name`, `issue.assignee.last_name`                             | The issue's assignee                    |
| `issue.team.name`                                                                                          | The issue's team                        |
| `issue.customer_portal_url`, `issue.customer_portal_link`                                                  | The issue in your customer portal       |
| `issue.custom_field.<slug>`                                                                                | An issue custom field                   |
| `issue.account.custom_field.<slug>`                                                                        | A custom field on the issue's account   |

### Account overview

| Variable                      | Value                        |
| ----------------------------- | ---------------------------- |
| `account.id`                  | The account's ID             |
| `account.name`                | The account's name           |
| `account.domain`              | The account's primary domain |
| `account.crm_account_id`      | The account's ID in your CRM |
| `account.custom_field.<slug>` | An account custom field      |

### Both locations

| Variable      | Value                                      |
| ------------- | ------------------------------------------ |
| `actor.id`    | ID of the Pylon user viewing the iframe    |
| `actor.email` | Email of the Pylon user viewing the iframe |

For select and multi-select custom fields, add `:label` to get the option's label instead of its stored value, for example `{{issue.custom_field.plan:label}}`.

## Issue View

Within the issue view, embed graphs, tables, internal dashboards, etc. from any webpage that supports embeddings, or build your own webpage and embed it.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2Fxg1NqxrXq9eHACybyPn4%2FCleanShot%202024-09-29%20at%2016.13.55.gif?alt=media&amp;token=ab264e6d-5532-4896-8ff8-5bf80d15a9bd" alt=""><figcaption></figcaption></figure>

## Account View

Within the account view, embed graphs, tables, internal dashboards, etc. from any webpage that supports embeddings, or build your own webpage and embed it. You can also add iframes to [account notebooks](/pylon-docs/account-intelligence/notebooks/blocks.md).

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2F3csl17lLZElWFHgdBBhq%2FCleanShot%202025-05-11%20at%2015.00.02%402x.png?alt=media&amp;token=f175336e-6b8e-4209-b463-7cb9ec3060fc" alt=""><figcaption></figcaption></figure>


---

# 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.usepylon.com/pylon-docs/developer/embedded-iframes.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.