Message Source Step

The Message Source Step is not available in the Step Library. Instead, a copy of this step is automatically present as the first step in any Junction Path. The purpose of the Message Source Step is to connect messages from another system, such as Salesforce or Office 365, to Y Meadows’ application. All new messages in the source system are copied into Y Meadows and sent on a Journey.

In addition to connecting a message’s source to Y Meadows’ application, the Message Source Step is also home to a number of outputs. These outputs can be used in the Junction Path as inputs to other steps and allow users to update source systems and take other actions that are common to all message journeys. For example, the status or priority of messages can be set in the source system to indicate that those messages are being processed by Y Meadows so that service agents do not pick up the tickets before they are ready.

One of the inputs to the Message Source Step is special and has a separate tab in the Input Editor. By clicking on the Message Retrievers tab users are able to pick specific folders (AKA: directories, queues, etc.) in the message source to get messages from. Users can even choose multiple different folders from the same source by pressing the “+” button to add new rows to the input.

Inputs

Connection

Most message sources require a username and password to access messages. In order to connect to the message source, users will need to have a “Connection” established in Y Meadows that contains the secret information needed to retrieve messages. Do NOT enter the secret information directly in Step Inputs. Instead, choose an existing Connection from a list of related credentials. Typically, Connections are set up by an administrator or IT employee.

Since a Connection is specific to a source system, once a connection has been created, users won't need to specify the source system.

Message Retriever

Get Message From:

After choosing the source system by selecting a specific connection, different "folders" such as directories, queues, etc. that are available to watch will appear in the drop-down menu for selection

In order to get messages from more than one folder, use the “+” button to add additional lines to the Input form.

Outputs

For each message that is processed by Y Meadows there will be certain information that is available for use by Steps in the Journey. The Outputs of the Message Source Step represent this information for each individual message as it is processed.

body

The main body of the message that is being processed is available in this output.

createdDate

The date that the message was either sent or created (depending on the source systems).

externalId

Source systems usually have an ID for each message which is necessary when updating the source system. This output is often used when configuring the inputs of steps that take action in the source system.

internalId

This output contains the unique identifier for the message that is used internally by Y Meadows.

senderEmail

The email address marked as the “from” address for the original message (when the message has a sender). Note that for some systems, such as web forms, the sender Email may be empty (null).

Note that this information can be manipulated by the sender so the value here may not be accurate.

senderName

When known, the full name of the person who sent the message. Note that this information can be manipulated by the sender so the value here may not be accurate.

subject

When applicable (eg: for email message) the subject line of the original message is available in this Output.