---
id: plugins-text
title: "Text"
summary: "The 5 plugins in Text: Handlebars, Json deserializer, Json serializer and 2 more."
audience: user
keywords: "Handlebars, JsonDeSerializer, JsonSerializer, RssAtom, Text"
---
# Text

Turn objects into text and text into objects. The **Json serializer** and **Json deserializer** convert between JSON and flow types; **Handlebars** renders templates for mail bodies, messages, XML or JSON; the **RSS/Atom parser** reads feeds; a **Text asset** keeps a piece of text in the flow for scripts to read.

```text
Http client → Json deserializer → ... → Handlebars → Mail client
```

## Plugins

| Plugin | What it does | Pins |
|---|---|---|
| [Handlebars](/documentation/plugins/text/handlebars) | Renders a Handlebars (Mustache-style) template with the input data and emits the result as a text record. Use it to build e-mail bodies, messages, XML or JSON payloads from flow data. | `Input`, `Output` |
| [Json deserializer](/documentation/plugins/text/json-de-serializer) | Parses JSON text into objects of a flow type. The target type is not configured: it is the type of the connection on the `Output` pin. A JSON array produces one message per element; the elements can form a batch. | `Input`, `Output` |
| [Json serializer](/documentation/plugins/text/json-serializer) | Converts the input object to JSON text. The records of a batch (e.g. one Sql query execution, one JSON array from Json deserializer, one file read) are serialized together into one JSON array when the batch completes; records without a batch become one JSON object each. | `Input`, `Output` |
| [RSS/Atom parser](/documentation/plugins/text/rss-atom) | Parses an RSS 2.0 or Atom feed (XML text) and emits one record per feed item. Typically placed after an Http client that downloads the feed. | `Input`, `Output`, `Property`, `Id`, `Title`, `ArticleLink`, `Summary`, `Categories`, `PublishDate`, `Authors`, `EnclosureUrl` |
| [Text asset](/documentation/plugins/text/text) | Stores a piece of text (template, query, message, configuration snippet) in the flow so that scripts and services can read it by name. It has no pins and is not part of the data path. | - |
