> ## Documentation Index
> Fetch the complete documentation index at: https://help.fanaura.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Journey editor

> Every stage in the capture journey builder, from link URL to publish.

Open the editor from **New journey**, **Edit journey**, or a journey card. The builder is a vertical canvas with stages connected top to bottom.

## Top bar

| Control | Label | Action |
| - | - | - |
| Back | **Back to Journeys** or chevron | Returns to the library. Unsaved work uses the outbox; you may see save status icons |
| Cloud icons | Save status | **Cloud check** means saved. **Cloud slash** means offline or save failed with retry |
| Preview | **Preview** | Opens the capture page preview |
| Publish | **Publish** or **Update** | Sends the journey live when validation passes. Confirm when the app asks |

## Stage 1: Link

You choose where fans land.

| Field / control | Purpose |
| - | - |
| **Public URL** / slug | The path on `fanaura.me` for this journey. The app checks availability and shows reserved or unavailable states |
| **Link enabled** | When on, the public URL accepts traffic. You can publish a link without turning on automatic replies |
| Link summary | Shows the full URL to copy or share |

## Stage 2: Details (capture form)

You define what you collect on the page.

| Control | Purpose |
| - | - |
| **Page title** and **Description** | Headline and body on the public capture page |
| **Fields** | Add or remove contact fields (email, phone, name, custom fields). **Add field** opens the field picker |
| Branding | Profile image and colors where shown in the canvas |
| **Automatic capture** | When enabled, certain sources create contacts without a full form submit where product rules allow |

## Stage 3: Replies (optional)

Automatic replies when someone uses a keyword on supported channels.

| Control | Purpose |
| - | - |
| **Keyword** | Word fans must send to trigger replies. Required for Instagram DM and similar triggers |
| Channel toggles | **Instagram**, **SMS**, **Email** as configured for your account. Each channel shows readiness (connected number, verified sender, Instagram connected) |
| **Endpoint** rows | Pick which journey link or message template sends when the keyword fires |
| Blockers | If publish is blocked, the app lists reasons such as missing texting approval, Instagram reconnect, or another journey already using the keyword |

Link-only publish is allowed when replies are not ready; the editor explains which parts can go live.

## Stage 4: Review

| Control | Purpose |
| - | - |
| Checklist | Summarizes link, fields, and reply settings |
| **Publish** | Confirms and activates. Live journeys update existing links when you choose **Update** |

## After publish

Live journeys appear in the library with status pills. Turn the link or replies off from the library stats panels or return to the editor.

## Errors

| Message | Meaning |
| - | - |
| **This journey could not be opened** | Invalid journey ID. Use **Back to Journeys** |
| Reply blockers (texting, Instagram, keyword conflict) | Fix the listed item in [Settings](/ios/settings) or another journey before replies can go live |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.