> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/edit-your-guideflow/steps/steps-library.md).
# Steps Library
Add content first, then orchestrate it across your demos. The Steps Library lets you pull in screens and steps from any of your existing Guideflow's into the demo you're currently building, so you never have to recreate the same content twice.
:chevrons-right: e.g. if you've already built a perfect pricing walkthrough in one demo, add those steps directly into any other demo without rebuilding them from scratch.
{% @guideflow/guideflow-embed requestedUrl="" %}
How to add steps from another guideflow
* Open the guideflow you're currently working on in the editor.
* Click Add Steps in the top left panel.
* Select Add steps from another Guideflow.
* Choose the Guideflow you want to pull steps from.
* Once the selected Guideflow opens, pick the screens or steps you want to add.
* Click Add Steps to confirm.
The selected steps are now added to your current Guideflow.
{% hint style="info" %}
You can pull steps from any Guideflow in your workspace, across folders and subfolders.
{% endhint %}
### 🔗 **Linking Steps**
By default, steps added from another Guideflow are **unlinked,** they are independent copies. Editing them in your current demo has no impact on the original Guideflow they came from.
You can choose to **link** or **unlink** steps depending on how you want to manage your content.
#### Linked steps
When steps are linked, they stay connected to their source. Any change made to a linked step automatically applies across every Guideflow it's been added to.
{% hint style="info" %} :chevrons-right: e.g. You've added a pricing walkthrough from Demo C into five other demos and linked them. Your pricing changes. You update the step once, and all five demos reflect the update instantly. No manual edits, no version drift.
{% endhint %}
Use linked steps when you're managing shared content across multiple demos, product updates, pricing screens, compliance flows and need everything to stay in sync effortlessly.
#### Unlinked steps
When steps are unlinked, they behave as standalone copies. Changes made to the step in your current Guideflow stay local, nothing is reflected back to the original Guideflow or any other demo using the same step.
{% hint style="info" %} :chevrons-right: e.g. You've added a pricing walkthrough from Demo C into Demo A. You update the step in Demo A to reflect a new price point. Demo C and any other demo using that step remain unchanged.
{% endhint %}
Use unlinked steps when you need to customize content for a specific demo without affecting anything else.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.guideflow.com/help/edit-your-guideflow/steps/steps-library.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.