> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/journey-maps/how-to-find-cards-in-a-journey-map.md).

# How to find cards in a journey map

Search the cards on a journey map by any word you remember and open the one you need with its details ready.

Jump straight to any card on a large journey map instead of scrolling and zooming to hunt for it.

Click **Find in map** in the top bar of the journey map editor (or press `CMD + K` on Mac, `CTRL + K` on Windows), type a word, and press `Enter`. Pick a result to go to that card on the map.

#### How to find a card in a journey map

{% stepper %}
{% step %}
**Open Find in map**

In the journey map editor, click **Find in map** in the top bar, or press `CMD + K` (Mac) or `CTRL + K` (Windows).

<figure><img src="https://1197101183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2For99xDEElfps9uMDY60K%2Fuploads%2Fgit-blob-61027e27fb6906c691495fffa2dfa1656c431920%2Fjourney-maps-find-in-map-01-top-bar-crop.png?alt=media" alt="The journey map editor top bar. A search field labelled Find in map, with a Cmd K hint, sits between the map title and the version history, favourite, and download icons, to the left of the Share button."><figcaption><p>Find in map in the editor top bar</p></figcaption></figure>

Before you type anything, the panel lists your recent searches and the most recently added cards. Click a recent search to run it again, or click **Clear** to empty the list.

<figure><img src="https://1197101183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2For99xDEElfps9uMDY60K%2Fuploads%2Fgit-blob-106f930814afeff48fc2c323cb08cc709010d9f9%2Fjourney-maps-find-in-map-07-recent-searches-crop.png?alt=media" alt="The Find in map panel with an empty search box. Card-type chips run across the top. Below them, Recent searches lists document, fraud, and approval with a Clear link, followed by a Recently added list of cards. A preview of the selected metric card shows on the right."><figcaption><p>Recent searches and recently added cards</p></figcaption></figure>
{% endstep %}

{% step %}
**Type a word and press Enter**

Results appear once you press `Enter`. Each result shows the matching text with your search term highlighted, the lane and the column or stage the card sits in, and the card type on the right.

<figure><img src="https://1197101183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2For99xDEElfps9uMDY60K%2Fuploads%2Fgit-blob-e8584c2d72175aad7618318b2b745f6fb8e506da%2Fjourney-maps-find-in-map-03-results.png?alt=media" alt="The Find in map panel over a journey map, showing results for the word document. Each result row has the card text with document highlighted in blue, the lane and column below it, and the card type, such as Text, Pain point, Opportunity, Solution, or Planning, on the right. The first result is previewed on the right with its lane and column and an Open button."><figcaption><p>Search results with the card's location and type</p></figcaption></figure>
{% endstep %}

{% step %}
**Narrow the results to one card type**

To see only one kind of card, click its chip above the results, for example **Opportunity** or **Text**. The chips match the card types on this map, and a greyed-out chip means none of the results are that type. Click the chip again to see every result.

<figure><img src="https://1197101183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2For99xDEElfps9uMDY60K%2Fuploads%2Fgit-blob-b4d14434a1e6a97ecc71cf565934d38355450a71%2Fjourney-maps-find-in-map-05-card-type-chip-crop.png?alt=media" alt="The Find in map panel with the Opportunity chip selected. Two opportunity results for document remain. Chips for card types with no matches, such as Stage, Icons, and Metric, are greyed out."><figcaption><p>Results narrowed to opportunities</p></figcaption></figure>
{% endstep %}

{% step %}
**Preview and open the card**

Click a result, or move through the list with the arrow keys, to preview the card on the right as it looks on the map. When you've found the right one, click **Open** or press `Enter`.

The panel closes, the map scrolls to the card and selects it, and the card's details panel opens so you can read or edit it straight away. To close the search without opening a card, press `Esc`.

<figure><img src="https://1197101183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2For99xDEElfps9uMDY60K%2Fuploads%2Fgit-blob-d81c260ce968964f7f47be3578623eb0ba78963f%2Fjourney-maps-find-in-map-08-opened-card-details.png?alt=media" alt="A journey map after opening an opportunity from the search. The map has scrolled to the card Real-time application tracker with document checklist, which is selected with its card toolbar showing. The Opportunity details panel is open on the right."><figcaption><p>The card selected on the map with its details panel open</p></figcaption></figure>
{% endstep %}
{% endstepper %}

Personas have the same search. In the persona editor, click **Find in persona** in the top bar or press `CMD + K` / `CTRL + K`. Your recent searches carry over between the two.

#### What Find in map searches

Find in map looks through the text on your cards, so you can search for any word you remember from a card:

* Text card content and step titles
* Pain point, opportunity, solution, and other portfolio item names and descriptions, including their IDs, such as PAI-14
* Metric names
* Titles of linked planning items and linked journey maps
* Embed link titles, slider labels, and icon labels

Small typos still find a match. A portfolio item placed on the map more than once shows up once for each place it's used.

<figure><img src="https://1197101183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2For99xDEElfps9uMDY60K%2Fuploads%2Fgit-blob-caaa786c9ce7f81fd611cd49c43693339d7897e2%2Frn-2026-10-find-in-map.png?alt=media" alt="Find in map results for document with the result PAI-14 Unclear document requirements during application selected. The preview on the right shows the pain point card with its description, Impact, Reach, and Cost scores, and the Pain Points lane and Column 2 below."><figcaption><p>A pain point found by a word in its title</p></figcaption></figure>

#### Why a card is missing from the search results

{% hint style="warning" %}

#### **Important: Find in map only searches cards you can see**

Cards hidden by an active filter or view are left out of the results, and the panel doesn't tell you a filter is on. If a card you know is on the map doesn't come up, click **Clear** in the bar above the map and search again.
{% endhint %}

<figure><img src="https://1197101183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2For99xDEElfps9uMDY60K%2Fuploads%2Fgit-blob-43b80f5e6c8f99d6dccf2c2f1492c94721f47b43%2Fjourney-maps-find-in-map-09-filter-active-results.png?alt=media" alt="Find in map returning a single result for document while a filter is active. The bar above the map shows Filter with a badge of 1, the filter Lanes: Step descriptions, Create view, and Clear."><figcaption><p>With a lane filter on, only cards in the visible lane are found</p></figcaption></figure>

If nothing matches at all, the panel shows **No results** for your search term. Check the spelling, or try a shorter word. For more on filters, see [How to filter a journey map](https://helpdesk.smaply.app/journey-maps/filtering-and-views/how-to-filter-a-journey-map.md).

#### Related topics

<table data-column-title-hidden data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-hidden data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>How to filter a journey map</strong></td><td>Show only the cards that match a lane, persona, tag, or portfolio item.</td><td><a href="https://helpdesk.smaply.app/journey-maps/filtering-and-views/how-to-filter-a-journey-map.md">Filter a map</a></td></tr><tr><td><strong>How to search across your account</strong></td><td>Find journey maps, personas, portfolio items, and metrics across all your workspaces.</td><td><a href="https://helpdesk.smaply.app/how-to-search-across-your-account.md">Search your account</a></td></tr><tr><td><strong>Journey map keyboard shortcuts</strong></td><td>Every shortcut for the journey map editor, with Mac and Windows keys side by side.</td><td><a href="https://helpdesk.smaply.app/journey-maps/journey-map-keyboard-shortcuts.md">Keyboard shortcuts</a></td></tr><tr><td><strong>How to add and edit cards</strong></td><td>Edit a card's content and use its details panel for tags, personas, and comments.</td><td><a href="https://helpdesk.smaply.app/journey-maps/cards/how-to-add-and-edit-cards.md">Add and edit cards</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdesk.smaply.app/journey-maps/how-to-find-cards-in-a-journey-map.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
