New actions 👓

You can now find three new actions in the journeys action sidepanel.

Add Traveller to journey

You can now add default values to your integrations so when the action is added to a journey the value is already set

1. You can now manage what fields are shown on the action in the journey builder so if you have a large endpoint with a lot of fields that are needed, you can simply hide those fields from the user working with the action in the journey builder. Simp

Additionally we changed the way you test your endpoints which are now performed in a modal where you first configure your test values and then secondly view the response.

Update Journey Fields

The table overview in journeys is an important part of your experience and value with Journeys. Each journey can have their own unique fields that can be shown in the table and are saved for each Traveller in that particular journey, we call these fields "Journey fields".

If you receive a piece of information from an action in a journey and you want to have it in the table overview, you can use this new action to put the value there fand show it in the overview.

Example of usage

You have a journey that has 2 custom journey fields "Last day of work" and "Reason for leaving". In the beginning of a journey the "Last day of work" is empty and fetched from a form in the journey. The tricky part is that in your journey, you can receive the last day of work date from two different Input forms, that are on two separate branches but you don't know which one will be run as they are conditioned. By using the Update Journey Fields action on both branches after the Input form action, you can put the received value in to the "Last day of work" field regardless of which branch is run.

Update Traveller Fields

Everyone that goes through a journey has
​Why did we make this improvement?

• A lot of third party software require input values that are always the same and the user creating the journey has no knowledge of what value are required so the default value feature helps with that
• Being able to manage what data is shown in the journey builder for the integration action will make the experience for the user a lot more straightforward as they only see relevant fields for the action