Journeys

Choose or write a journey ​

A journey tells Journeys where to begin, what outcome to verify, and any values it may use. Start with a catalog journey when it fits; write a custom journey when the behavior is particular to your product.

Catalog journeys ​

Catalog journeys are maintained by Journeys. Their name, start path, instructions, variable definitions, outputs, and step budget are locked so updates can remain consistent. You can supply variable values, choose the schedule, and teach the journey on your own site.

If you need to change the definition, choose Duplicate & edit. Journeys opens an editable custom copy. The copy is not stored until you choose Save, and it begins as a new Draft with its own memory.

Deleting a catalog journey removes it from the site. You can add a fresh copy from the catalog later, but its former values and learned memory do not come back.

Custom journeys ​

Choose Write your own journey, or open Add journey → Write your own journey on an existing site. A definition has:

  • Name — a short description of the behavior being watched.
  • Start URL — the first page Journeys opens. It must stay within the site.
  • Instructions — the outcome and boundaries for the browser agent.
  • Variables — reusable values, including values that should be secret.
  • Outputs — values this journey may publish to a following journey.
  • Memory — learned advice from successful runs, once any exists.
  • Settings — the step budget that limits how far one run may go.

Choose Save to store the definition. Saving does not run or schedule the journey. Choose Run for an attended attempt; the editor can run an unsaved definition when it has a start URL and instructions, but that ad-hoc run will not appear in the site's History.

Write instructions that can be judged ​

Describe the result a person should be able to observe, and identify important limits. For example:

Search for . Open the matching product and confirm its product page shows a price. Do not add it to the cart.

Prefer an observable finish over a list of pixel-level clicks. Mention actions that must not be taken, especially submits, purchases, messages, deletions, and changes to account data. Use a variable for a value that changes or must be protected.

A journey is browser automation against your real product. Use a test account and test data when the flow can write data, incur a charge, notify a person, or use a paid seat.

Change or remove a journey ​

Open a journey to edit its definition. Existing memory is not automatically cleared when the instructions change, so inspect it and remove advice that no longer applies.

For a watched custom journey, Stop watching removes its schedule and any dependency while keeping the definition, variables, secrets, and memory. Delete the custom journey from its editor only when you also want to remove that saved definition and its memory.

A journey cannot be removed while other journeys are set to run after it. Journeys names those followers; change them first, then try again.