Assign a Conversation

In Front, a conversion can be assigned to a user. The Front - Assign a Conversation step makes it possible to accomplish this as part of a Y Meadows automation.

Either a Message ID or a Conversation ID can be used to identify the conversation that will be assigned. The user is identified by email address, where the email address must be from a front user who has access to the conversation. If the email address does not match these criteria then the step will fail with an error.

Input

Connection

Select a connection that contains the passwords or keys that are needed to access a specific Front instance. Since users can not enter secret information directly into the step input, a connection must be created in advance. Generally, connections are created by Administrators or IT Staff who have access to the necessary credentials.

Message ID (need EITHER this or Conversation ID)

The ID of a single message in the Front system. Typically this is taken from the externalId output from the first step in a Journey.

Users do NOT need to provide both a Message ID and a Conversation ID but one of them must be provided. Conversation ID (need EITHER this or Message ID) Other Front steps may provide a Conversation ID that can be used to fill in this input. This step acts on a Front conversation but is able to figure out the conversation from a Message ID if one is provided. If users have a Conversion ID but not a Message ID this step will still work as expected.

If both a Message and Conversation ID are provided then the Conversation ID will be used.

Assignee Email

The Email address of the user that the ticket will be assigned to.

Outputs

message

A message about the step's execution that is often helpful in tracking down the cause of any errors.

success

This will be True if a comment was successfully added and False if one was not.