--- title: "Create a journey | Darwinium" slug: "creating-and-editing-journeys" description: "Create a journey to define a flow such as registration, authentication or payment." updated: 2026-10-16T09:37:22Z published: 2026-10-16T09:37:22Z canonical: "docs.darwinium.com/creating-and-editing-journeys" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.darwinium.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a journey Create a journey to define a flow such as registration, authentication or payment. The definition connects the steps to process, the data to map and the assessment logic to run. See [Journeys, steps & events](/docs/journeys) if these terms are new. In **Workflows**, work in the repository for your selected test node. For a website, the [Journey Recorder](/docs/journey-recorder) can generate steps as you browse; this article explains manual creation and the configuration you should review either way. The result is a journey file ready to build and deploy—not a live change as soon as the file is saved. ## Creating a new Journey To create a new Journey, add a file into the ***root*** of the repository. Journey files in root folder Make sure to place all journey.yaml files in the project root folder Where the journeys.yaml file is ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image-1656908239060.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A24%3A51Z&se=2026-11-23T00%3A24%3A51Z&sr=b&sp=r&sig=oe2cNbTZmJipBn88I4HrrPR465pfy13eyTvjmjEmnAg%3D) The new Journey file must have the file extension ".journey.yaml". ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image-1656908402018.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A24%3A51Z&se=2026-11-23T00%3A24%3A51Z&sr=b&sp=r&sig=FnUo0OnSqgzJk2qnTvNll1damf6YZOCMhgXfTbNChb4%3D) If you accidentally create the file in a folder, you can simply drag the file to the root folder. ## Activating your new Journey To include the journey in a build, add it to "journeys.yaml" in the repository root. Review and deploy the built revision before expecting the journey to process live traffic. ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image-1656908461495.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A24%3A51Z&se=2026-11-23T00%3A24%3A51Z&sr=b&sp=r&sig=HApwBL8lW6%2FY35c1rKJ9WPVeN%2BFxogvJwmm4ydWxUYA%3D) ## Setting up a new Journey Click on your newly created Journey file in the File Explorer to launch the Journey Editor. A newly created Journey file must have some initial configuration done before it can be used. Click on the Settings icon in the top right of the Journey Editor. ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image-1656909557317.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A24%3A51Z&se=2026-11-23T00%3A24%3A51Z&sr=b&sp=r&sig=scAakeMsFalwApR4Li58tEc63rySnW73RL7pbziC2H0%3D) Give the Journey a name to uniquely identify it within the Journey Name setting. ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image-1656908612570.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A24%3A51Z&se=2026-11-23T00%3A24%3A51Z&sr=b&sp=r&sig=pWwsGHq%2FWJJin5gsdUApur29slMnKB1Tp7rz7mGTNS8%3D) ### Journey Cookie Configuration Request cookies are used by Darwinium for both Journey Management and Device Identification. Darwinium can create new Cookies or be instructed to use existing ones. See [profiling article](/v1/docs/creating-and-editing-journeys#journey-cookie-configuration) for further advice on configuring those cookies. - Session cookie helps resolve a `journey_id` ; not needed if using a `*_tie` attribute or `journey_id` direct - Device cookie helps resolve a `profiling.device.identifier' ; highly suggested on web, not needed on mobile SDK ## Adding a Step When a Journey is first created is is empty. Use the Add button within the Journey Editor to add a new Step to the Journey. ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image-1656908569097.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A24%3A51Z&se=2026-11-23T00%3A24%3A51Z&sr=b&sp=r&sig=1TdNjbVa4Y%2FF1lNQkQObwDeGLOoUpP4oB88%2BJeRbacA%3D) Clicking on the newly created step will open the Step Editor within the right hand side of the Journey Editor. ![](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image-1656912311790.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A24%3A51Z&se=2026-11-23T00%3A24%3A51Z&sr=b&sp=r&sig=KkFyJMogeh0gO1e3LsIcsPGAM%2Bu73nM4HtcQHrzCOzM%3D) You are now ready to Edit this and other steps on the journey. See: [Creating and Editing Steps.](/v1/docs/creating-and-editing-steps) ## (optional) Remove validation for non-card attributes Darwinium has platform wide protection to refuse consuming potential card number into unrelated input attributes. - The event will still process, but attribute will be treated Null and will return a `422 Unprocessable Entity` - Specific details are given in response attribute: `invalid_input_attributes` ```json "invalid_input_attributes": {        "identity[ACCOUNT].account_number.account_number": "validate NonCreditCard failed A potential credit card number was provided. This cannot be processed by darwinium at this time. at line 27 column 40"    }, ``` However: some legitimate non-card attributes can require to be passed into an input field (eg. a generic customer number taking 16 digit format). The validation on **confirmed non-card** input attributes can be skipped by listing them in the journey file: ```yaml confirmed_non_card_attributes:  - identity[BENEFICIARY].account_number.account_number  - identity[ACCOUNT].account_number.account_number ``` Continued assurance your side Including attributes under confirmed_non_card_attributes is committing that now and continuously, no card details will ever appear under the mapping of those specific attributes. After configuring the steps, follow [Deployment confirmation](/docs/deployment-confirmation) and find a test event in [Investigations](/docs/investigations-overview).