Add Tags to a Conversation

The Front - Add Tags to a Conversation step is used to add one or more Front tags to a conversation. This is often used to enable additional automation that is managed by Front. However, tags in Front have many other uses too. For more information about tags in Front see their tags help page.

Inputs

Connection

Users should select a connection that contains the passwords or keys that are needed to access a specific Front instance they desire to use. 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

The externalId output from a Message Retriever step that is connected to Front will contain the Message ID of the message. This is usually the value used for this input.

Users do NOT need to provide both a Message ID and a Conversation ID but you do need to provide one of them.

Conversation 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 users provide BOTH a Message and Conversation ID then the Conversation ID will be used.

Tags

This field requires a list of tags. In the Y Meadows expression editor a list looks like this:

["tag 1", "tag 2", "tag 3"]

Even if users have only one tag it still needs to use the square brackets like this:

["tag 1"]

Users need to match the name of the tag from Front, including proper capitalization. If the step is failing check to make sure that the tags are an exact match in Front.

Outputs

message

The "message" returned by this step is valuable only for troubleshooting when something goes wrong. It will contain a short message from Front about the success or failure of the attempt to add tags to the conversation. If trips are failing at this step users may be able to learn more about the reason for the failure by looking for the message in the trip report (found in the Analytics section of the application)