> For the complete documentation index, see [llms.txt](https://documentation.alpaco.email/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.alpaco.email/template/input-groups/input-types/feed.md). # Feed A **Feed** input is great for when you want to give users the ability to dynamically access any type of feed, be that a product feed, article feed or anything similar. Then extract those values and insert them into your emails as you see fit. \ The format is irellevant, whether that is XML, JSON, as long as it's structured. \ A Feed input can be used in a normal input group or inside a [repeatable](/template/input-groups.md#repeatable). Works great for: * Product feeds * Article feeds ### Template Editor When creating a new **Feed** input, you'll need to provide the URL for the raw access to your feed. Upon doing so, a list of output fields gets propagated based on the feed and converted into usable liquid fields ready to be inserted into your template. \ \ Because all fields are transformed into liquid fields, all liquid filters becomes available to moderate the output to fit into your template. All field names are directly interpreted from the feed, except images, that gets it's own naming convention `{{ .feed.images.url }}` for the tradeoff of being able to use all abilities available in the [image settings](/template/input-groups/input-types/image/image-settings.md) filter.\ \ Lastly you get two dropdown options to configure the dropdown lists in the Email Editor.

In this example we see a product feed with multiple fields to simply click to use in your code.

In the code we see multiple examples of using the output fields in combination with liquid filters, ensuring the description is not too long, calculating the height of a container, based on the altered image dimensions ect.

### Email Editor