> For the complete documentation index, see [llms.txt](https://sygnal.gitbook.io/sygnal-webflow-components/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sygnal.gitbook.io/sygnal-webflow-components/cc/sygnal-components/embed.md).

# Embed ✅

### Overview

{% embed url="<https://www.loom.com/share/270e9dce6762410dad582cab1739257e>" %}

## Usage Notes&#x20;

1. Drop your Embed element on the page
   1. Create the content you want
   2. Where you want custom-inserted values, use the format `{{wf name}}` where `name` is your own chosen name.  No spaces, but hyphens and underscores are permitted.&#x20;
   3. On the Embed element itself, add a custom attribute for each name.  If you have an embedded field called `bob` , create an attribute named `bob` . The value is what will be inserted inside of your Embed content.&#x20;
2. Create a Component from your Embed element&#x20;
   1. Bind your custom attribute value to a new property on your Component
   2. Set those properties, or bind them ( Collection page, collection list, parent component... )&#x20;
3. Add the Sygnal Embed code component to the page&#x20;
   1. Move your Component into the Embed code component slot&#x20;

*Done!* &#x20;

The code component will now handle the mutation of the property-bound attributes into your Embed content automatically.&#x20;

## Technical Notes

Examples of Webflow's native syntax;

{% code overflow="wrap" %}

```
<li>{{wf {"path":"name","type":"PlainText"} }}</li>
<li>{{wf {"path":"description","type":"PlainText"} }}</li>
<li>{{wf {"path":"latitude","type":"Number"} }}</li>
<li>{{wf {"path":"fullSlug","type":"FullSlug"} }}</li>
<li>{{wf {"path":"created-on","transformers":[{"name":"date","arguments":["MMM DD, YYYY"]}],"type":"Date"} }}</li>
```

{% endcode %}


---

# 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://sygnal.gitbook.io/sygnal-webflow-components/cc/sygnal-components/embed.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.