> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/integrations/how-to-use-embed-integrations.md).

# How to use embed integrations

Embed live content from tools your team already uses, like a Figma frame, a Google Doc, a Miro board, or a YouTube video, directly onto a journey map card. Embeds are link-based: paste a share link and the content renders in the card.

Unlike metrics and planning integrations, embeds need no account-level connection and no authentication setup. There's nothing to switch on in **Account Settings**. Each embed works from the share link you paste, so the only thing that decides whether it renders is the link type and the source's own sharing settings.

#### Supported sources

Smaply embeds content from these sources:

* **Figma** - embed a specific frame or file
* **Google Docs, Google Sheets, Google Slides** - embed a document, spreadsheet, or presentation
* **Miro** - embed a board or a single frame
* **Mural** - embed a mural
* **YouTube** - embed a video
* **Power BI** - embed a report
* **Tableau** - embed a dashboard
* **Monday.com** - embed a workspace view
* **SharePoint** (Excel, Word, PowerPoint) - embed an Office file
* **OneDrive** (Excel, Word, PowerPoint) - embed an Office file

Generic web URLs also work. When a page exposes the right metadata, the embed renders as a rich link preview.

#### Get a shareable link from each source

The link you paste has to be one that anyone with access to the map can open, not a private editing URL tied to your own login. Open the source, set its sharing so the people who will view the map can reach the content, then copy the link the source gives you for sharing or embedding. Specifics differ by source.

<details>

<summary><strong>Figma</strong></summary>

In Figma, select the frame or file you want, open the share dialog, and turn on link sharing so anyone with the link can view. Copy that share link. To embed a single frame rather than the whole file, copy the link with the frame selected.

</details>

<details>

<summary><strong>Google Docs, Sheets, and Slides</strong></summary>

In the Google file, open **Share**, set **General access** so anyone with the link can view, and copy the link. If access stays restricted to named people, viewers without those Google accounts see a request-access screen instead of your content.

</details>

<details>

<summary><strong>Miro and Mural</strong></summary>

In Miro or Mural, open the board's share settings and enable public or anyone-with-the-link access, then copy the share link. A board left private to your team renders blank for anyone outside it.

</details>

<details>

<summary><strong>YouTube</strong></summary>

Copy the video's URL from the address bar or the **Share** button. Set the video's visibility to Public or Unlisted; a Private video does not play for other viewers. No further sharing setup is needed.

</details>

<details>

<summary><strong>Power BI, Tableau, and Monday.com</strong></summary>

Use the link these tools generate for sharing or embedding a report, dashboard, or view, and make sure it's set so your map's viewers can reach it. Access to the underlying data still depends on each viewer's own permissions in the source tool.

</details>

<details>

<summary><strong>SharePoint and OneDrive (Office files)</strong></summary>

SharePoint and OneDrive embeds use an embed code rather than a plain share link. In the Office file, generate the embed code, and set the file's sharing so your viewers can open it. Paste the code's source URL into the embed.

</details>

<details>

<summary><strong>Any other web page</strong></summary>

Paste the page's URL. Pages that expose Open Graph metadata render as a rich link preview; others fall back to a plain link.

</details>

#### When an embed does not render

If an embed shows a blank card, a permission prompt, or a login screen for the source tool, the cause is almost always the source's sharing setting, not Smaply. Whether embedded content is visible depends entirely on the source platform's own sharing and privacy settings, and this applies to viewers of a shared HTML view as well as to anyone without an account on the source tool.

Open the source, confirm sharing is set so the people viewing the map can reach the content (typically anyone-with-the-link or public), copy the link again, and re-paste it. If the link works for you because you're signed in to the source but not for a logged-out viewer, the sharing setting is still too restrictive.

#### Related topics

<table data-view="cards"><thead><tr><th>Article</th><th>What it covers</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td>How to use embed cards</td><td>Add an embed card to a journey map and switch its display mode</td><td><a href="/pages/OZrRWKElbHcwoxQO8mln">/pages/OZrRWKElbHcwoxQO8mln</a></td></tr><tr><td>Set up your first integration</td><td>Connect a metrics or planning tool at the account level</td><td><a href="/pages/MnIIaFvymKzpE7B98hdU">/pages/MnIIaFvymKzpE7B98hdU</a></td></tr><tr><td>How to manage integrations</td><td>States, disconnect, and switching auth methods for connected tools</td><td><a href="/pages/eVJNZWbpULcbx2YE06fQ">/pages/eVJNZWbpULcbx2YE06fQ</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdesk.smaply.app/integrations/how-to-use-embed-integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.