Skip to main content
When the customer story already exists somewhere else, do not start from a blank canvas. Use AI import to get to a first draft quickly, then spend your time fixing scope, naming, and evidence instead of rebuilding the whole map by hand. If the source material is best prepared from a terminal or coding agent, use CLI quickstart instead. The CLI can create a verified first journey from a public website, private brief, or standard input.

​
What AI import creates

AI import creates a draft journey from one source you already trust. Custory can draft:
  • a journey name
  • likely stages
  • likely steps
  • initial structure your team can review
This is a drafting tool, not a final answer. Review the result before the rest of the team uses it.

​
Current starting paths

Custory currently supports these journey-creation paths from the dashboard: If a connected source is not set up yet, connect the integration first. If the source is not available in your workspace, use URL import, a template, or AI chat instead.

​
Import a journey

  1. Start a new journey from the dashboard.
  2. Choose From website or URL, From GitHub, From Notion, or From Figma.
  3. Enter the URL or select the connected resource.
  4. Fill in What should this journey cover? with a short scope note.
  5. Create the journey.
  6. Open the draft and clean it up before sharing it broadly.
The context field is optional, but it usually 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 leave too much room for the importer to guess wrong.

​
Choose the right source

The best import is usually the narrowest source that already describes one real customer journey. Prefer:
  • one repo over a broad monorepo
  • one specific docs page over a generic homepage
  • one focused Notion page over a mixed workspace
  • one relevant Figma file over a large design library
If you give the importer a source that mixes several flows together, the draft usually comes back broad, generic, and noisy.

​
Source guidance

​
Website or URL

Use a URL import when the public product story already explains the journey well. This works best for:
  • self-serve signup flows
  • pricing and plan-comparison paths
  • onboarding or setup docs
  • public help content that describes activation clearly

​
GitHub

Use GitHub import when the most useful source is the product itself. This works best when:
  • the product already exists
  • one repository maps closely to the customer flow
  • engineering reality should shape the first draft
Before importing from GitHub:
  1. Connect the GitHub integration.
  2. Select the repository you want to use.
  3. Add a short note describing the journey scope.

​
Notion

Use Notion import when the clearest source is already documented. Good examples:
  • research notes
  • discovery summaries
  • workshop writeups
  • onboarding documentation
Choose the page or database that is closest to one real flow. Broad internal workspaces tend to produce weaker drafts.

​
Figma

Use Figma import when the structure of the experience is easiest to understand from the design itself. This is useful for:
  • early-stage products that are still design-heavy
  • new flows that are not fully shipped yet
  • redesign work where the screens explain the journey better than the current implementation
Paste a Figma file URL or file key in the import flow. Custory reads the text in that file so the draft can reflect the flow shown in the design.

​
Clean up the draft

Do not treat the draft as ready for the rest of the team. Do this first:
  1. Rename anything vague.
  2. Remove stages that do not belong.
  3. Rewrite steps from the customer’s point of view.
  4. Add or correct the first items.
  5. Link the right persona if one matters.
Review the draft before sharing it with the wider team.

​
Example: trial-to-paid onboarding

Say your team wants to map trial-to-paid onboarding. You already have:
  • a pricing page
  • a help article for setup
  • one repo for the onboarding flow
The best move is usually to pick the source that reflects the customer experience most directly. If the public setup path is already clear, start with the docs page or URL. If the product flow is clearer in the codebase, use the repository instead. After the draft appears, trim it until it sounds like your product and matches what customers actually experience now.

​
Limits

  • AI import creates a draft structure. It does not validate that the journey is true.
  • Broad or mixed sources usually create broad or mixed drafts.
  • Connected imports require an active integration in the workspace.
  • Figma import uses the file URL or key you provide; it does not browse a file picker.
  • The draft becomes more useful after you add items, evidence, and the right persona.

​
Next step

Read Your first journey (step by step) to turn the imported draft into a map the team can actually use. If your source material is scattered across notes and docs instead of one clean import source, read Migrating to Custory.