Steps

What are Steps:

Steps are individual processes (often ones that perform an activity or action) that can be put together to create Paths. A Step is unique to the Journey that it is in as it consists mainly of data mapping and configuration of which choices to make when calling the step service.

Each "bubble" in the Journey represents a step in a Path.

While steps may contain internal logic, they can not directly control the flow of a message through a Journey. The logical flow is defined outside the steps and takes action based on data (slots or entities) that travel with the Message.

Note: Keeping steps simple will allow them to be more scalable across many different paths and Journeys

Configuring steps in Y Meadows is fairly simple for users with varying degrees of technical capabilities.

Configuring Steps:

‌Each step can be configured by clicking on the fly out toggle in the top right corner:

Or by clicking on an individual field:

Users will see input options on the left side:

‌Simply drag and drop an input into the field, hit save, and the value will be fixed for that field:

Once all of the required fields are filled out, the step is ready for use.

Built-in Steps:

NAME	FUNCTION
Source Step	The Source step is the source of the messages being brought into Y Meadows from the users communication channels.
Junction Step	The Junction steps are merely a representation of the model in the Path flow. They do not require any configuration.
Review Step	The Review Step is where you will set up the review process in the Journey. The Review process is where the message will be sent to a queue for an agent to review prior to triggering the rest of the Journey steps.
Go-To Step	Link steps allow you to jump from one branch to another branch. This could help reduce the amount of steps you need to build in a Journey.
Decision Step	Decision Steps manage the logic flow in the Journey. Decisions are created using FEEL expressions that dictate different directions the Path will take.
Exit Step	The Exit Step is used for finishing a Path before the rest of the Journey Path is over. It differs from a Fallback Path because it can be configured to add metadata and information to a ticket, as well as routed to a specific queue.

Integration Steps:

Y Meadows is constantly growing their library of integrated steps. Currently, Y Meadows has built out integrations with popular platforms like Salesforce, HubSpot, Front and Zendesk. Each one of those integrations has a number of custom steps. Explore those steps here:

pageSalesforcepageHubspotpageFrontpageZendesk