The Journey Library is a catalog of journeys built by Xenia, ready to import into your workspace. Importing one opens it in the Journey Orchestrator as a normal draft journey that you own and can change freely.
Why start here
A template is faster than a blank canvas, but the better reason is that it shows the shape of a working journey: which trigger to use, where the wait belongs, what to check before sending, and where the branch goes. Reading two templates teaches more about the node model than reading the node reference.
Importing
Browse by category
Templates are grouped by category. Shopify merchants see the Shopify category, since those are the templates that can run against a store connection.
Open the template
Choose a template to open it in the Journey Orchestrator.
Make it yours
Rename it, point the nodes at your connectors, replace the placeholder copy with your content, and write the briefing.
Save it
Saving creates a journey in your workspace. The template itself is untouched, so you can import it again for a different variation.
Importing does not publish anything. The journey goes through the same path as anything you build by hand: briefing, simulation, review, approval, publish.
What to check before publishing an import
Templates ship with placeholders. Before it goes to review, confirm:
- Connectors. Every channel node points at a connector configured in the environment you will publish to.
- Copy. Placeholder subject lines and message bodies are replaced with yours, and
every
{{variable}}in them actually exists on that path. - Timing. Waits reflect your customers rather than the template's defaults.
- Audience. Rules and audience checks match how your data is actually shaped.
Then run it in Simulation before sending it for review.
Related
- Journey Orchestrator for the node reference
- Node Library to swap placeholder configuration for your saved instances in one step