Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt

Use this file to discover all available pages before exploring further.

AI journey imports help you start from real source material instead of a blank canvas. This is one of the fastest ways for small teams to get into a useful workflow, especially when the product story already exists across a website, repo, workspace doc, or design file.

​
When to use AI import

Use AI import when:
  • The source already exists elsewhere
  • You want a strong first draft quickly
  • The team would rather edit than structure from zero
This is especially useful for:
  • Founder-led teams with product context already in their heads and docs
  • Product-led teams with onboarding or activation material spread across several tools
  • Teams documenting a flow that already exists in the product

​
Current starting paths

Custory supports these journey creation paths:
  • From website or URL
  • From GitHub
  • From Notion
  • From Figma
The fastest path depends on where the most truthful source already lives.

​
Import from a website or URL

Use URL import when the public product story is already visible on your website or documentation. This works well for:
  • Marketing-site onboarding flows
  • Self-serve signup and pricing experiences
  • Public docs that explain setup or activation
Use it when you want Custory to infer the customer-facing flow from what a user can actually see. This path is a strong fit when the core experience is product-led and the website already explains the value, setup path, or product structure.

​
Import from GitHub

Use GitHub import when the most useful context lives in the product itself:
  • Repositories
  • Product implementation details
  • Internal structure reflected in the codebase
This is especially useful when:
  • The product already exists
  • The team wants a draft grounded in real implementation
  • Engineering context should shape the early journey map
Before importing from GitHub:
  1. Connect the GitHub integration
  2. Select the repository you want to import from
  3. Add a short note about what the journey should cover

​
Import from Notion

Use Notion import when the most useful source material is already documented. Custory can import from:
  • Notion databases
  • Notion pages
This is often the best starting path when the team already has:
  • Research notes
  • Support summaries
  • Discovery writeups
  • Product plans
  • Journey fragments in docs form
Choose the specific page or database that is closest to the customer flow you want to map. Import quality is better when the source is focused.

​
Import from Figma

Use Figma import when the product flow is easiest to understand from designs or prototypes. This is useful for:
  • Early-stage products that are still design-heavy
  • New flows not fully shipped yet
  • Teams planning a redesign and wanting the journey draft before implementation
Figma is best when the structure of the experience matters more than the metadata around it.

​
Add journey context before you run the import

In the import flow, Custory lets you describe what the journey should cover. Use that field. It improves the draft. Good examples:
  • Onboarding journey for new self-serve users
  • Trial-to-paid flow for first-time workspace owners
  • Activation journey for teams connecting Slack and inviting their first teammate
Weak prompts such as customer journey or main flow give AI too much room to infer the wrong scope.

​
What Custory does during import

The AI-assisted import flow is designed to turn source material into a working first draft. In practice, Custory can:
  • Derive a concise journey name
  • Identify likely stages
  • Identify likely steps
  • Create initial journey content from imported evidence
The result is a draft to refine, not a final artifact to trust blindly.

​
How to prepare source material for better results

Import quality improves when the source is:
  • Narrow enough to describe one journey clearly
  • Current enough to reflect the real product
  • Concrete enough that the AI can infer actual customer moments
Before importing, prefer:
  • One repo over many repos
  • One focused Notion page or database over a large mixed workspace
  • One relevant Figma file over a broad design library
  • One clear URL over a generic homepage if a more specific page exists

​
What to do right after the import

Do not invite the team into the draft immediately. First:
  1. Rename anything vague
  2. Remove stages that do not belong
  3. Rewrite steps from the customer point of view
  4. Add or correct items using real evidence
  5. Link the right persona
The best imported journeys usually get a 15 to 30 minute cleanup pass before becoming the team’s shared map.

​
How to choose between URL, template, and integration import

Use URL when the public experience explains the flow best. Use a template when you need structure but do not yet have one strong source. Use a connected import when product, research, or design artifacts already contain the real story.

​
Common mistakes

​
Importing from the broadest source available

A focused source almost always produces a better draft.

​
Skipping the journey-context prompt

The import is better when you tell Custory what you are trying to map.

​
Treating imported structure as validated truth

Imported stages and steps should be reviewed before the team starts using them operationally.

​
Importing once and never grounding the draft in evidence

The map becomes valuable only when you attach real items, decisions, and follow-up work.