# Embed Flowline

Embed Flowline explains how this part of Flowline works and how to use it in a real workflow. This page is dummy content for testing the Cloudairy wiki: structure, navigation, search and rendering.

<figure id="6bbabc8c4606" data_color="rgb(0, 0, 0)" data-type="blockquoteFigure" style="
          // background-color: rgba(0, 0, 0, 0.1);
          background-color: "#FFFFFF";
          border-left: 3px solid rgb(0, 0, 0);
          ">
<div><blockquote><p data-id="19ce46c2-c348-48c2-b505-45863e23d662"><strong>Note:</strong> Flowline is a fictional automation product. Section: <strong>Connect</strong>.</p></blockquote></div>
</figure>

## Prerequisites

- A Flowline account (cloud or self-hosted)
- Editor access to the project
- About 5 minutes

## How it works

Every workflow starts with a **trigger**, passes *items* from node to node, and ends when the last node finishes. Embed Flowline fits in the middle of that chain: it receives items, does its work, and hands the result to the next node. Use `$json` to read the current item and `$node["Name"]` to reach an earlier node.

<img src="https://picsum.photos/seed/embed-flowline/1200/640" data-width="100%" styling-key="" data-align="center" data-flip-vertical="false" data-flip-horizontal="false" alt="Embed Flowline — sample screenshot" data-original-url="" data-crop-mode="" data-image-radius="" data-show-border="" data-border-color="rgba(0, 0, 0, 0)" data-border-type="solid" data-border-width="1px" data-key="img" data-userdata="">

## Step-by-step

1. Open the workflow editor and select **Add node**.
2. Search for **Embed Flowline** and add it to the canvas.
3. Fill in the required parameters (see the table below).
4. Select **Test step** to run it with sample data.
5. Check the output panel, then **Save** the workflow.

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| Name | string | Yes | A label shown on the canvas |
| Mode | option | Yes | `run once` or `run per item` |
| Timeout | number | No | Seconds before the step fails (default 122) |
| Retry on fail | boolean | No | Retries up to 3 times with back-off |

## Example

```json
{
  "name": "Embed Flowline",
  "nodes": [
    { "type": "trigger.webhook", "path": "/embed-flowline" },
    { "type": "core.set", "values": { "status": "ok", "retries": 3 } }
  ],
  "active": true
}
```

<figure id="6bbabc8c4606" data_color="rgb(0, 0, 0)" data-type="blockquoteFigure" style="
          // background-color: rgba(0, 0, 0, 0.1);
          background-color: "#FFFFFF";
          border-left: 3px solid rgb(0, 0, 0);
          ">
<div><blockquote><p data-id="a5fe2330-e6e1-4f1b-b8d4-8e463d9ccdd4"><strong>Tip:</strong> Press <strong>Ctrl</strong> + <strong>Enter</strong> to run the current step without leaving the keyboard.</p></blockquote></div>
</figure>

## Troubleshooting

| Symptom | Likely cause | Fix |
| --- | --- | --- |
| Step shows *No output* | The previous node returned zero items | Pin sample data on the previous node |
| `401 Unauthorized` | Expired credential | Reconnect it under **Credentials** |
| Execution times out | Large payload | Split items with **Split Out** |

## Related

- **Build your first workflow**
- **Expressions**
- **Error handling**

## Edited on github.com

This section was written in **GitHub's web editor** to test that a change made on GitHub shows up in Cloudairy Docs.