The user's distinct_id. If you are sending Events to Mixpanel in addition to Profiles, this property value should be identical to the distinct_id property attached to events so that you can connect events to profiles. Tell me more about distinct_id.

Properties contain information about the profile. For example, for a user profile, properties can be things like an email address, where they came from, or their age. These properties allow you to drill down to very specific segments of users/customers and learn more.

Properties are sent as key-value pairs where the key is the property name and the value is the property value. Tell me more about properties.

Certain property keys are special/reserved. For example, if you include the $email property, you can start sending targeted email notifications using Mixpanel's Notifications product. Other examples of special properties are $name, $phone and $unsubscribed. Learn more about Special/Reserved properties .

Since this field is not option, if you don't pick a user, the trigger will fire whenever a conversation is assigned to any agent.

If you add more tags, conversation must have all of them for this trigger to fire.

Please enter custom field name to the left input field as you see in the the Help Scout application. The right side should contain value, again as you see it in the Help Scout application. Both input fields are case insensitive. If you enter more custom fields, conversation must match all of them for this trigger to fire.

Select which mailbox you'd like to watch for new customers.

Conversation ID where the note will be added. You can use Find Conversation to get the conversation ID or get the ID from a different source (New Conversation trigger for example).

Text of the note. You can use HTML markup.

User who is adding the note. The user must be authorized to add notes into the mailbox where the conversation in question exists, otherwise error will be returned.

Customer's email. Please note that if there is existing customer with this email, this action will end up with an error.

Phone entry - the left input is the email type or location. Supported values are fax, home, mobile,other,pager,work.

Chat handle entry - the left input is the chat handle type or location.aim, gtalk, icq, msn, other, qq, skype, xmpp, yahoo.

Social profile entry - the left input is the account type, supported values are aboutme, facebook ,flickr,forsquare, google, googleplus, linkedin, other, quora, tungleme, twitter, youtube.

URL of a website associated with the customer.

Information about the customers. The value is displayed as Notes in the Help Scout UI.

Following fields form a customer's address. The fields are optional but once you enter information into one field, you need to fill all other fields with the exception of address lines.

A name for this Event. For example, 'Brand Mentioned in Tweet' or 'Payment Made'. Tell me more about Events.

A way to uniquely identify your users (or more generally, profiles). If you are sending Profiles to Mixpanel in addition to events, this property value should be identical to the Distinct ID property attached to the Profile so that you can connect events to people records. Tell me more about distinct_id.

Event Properties are bits of extra information that you send along with your Events describing the details of that action. They are usually specific to the Event they’re describing and don’t apply universally to other Events. Leveraging Event Properties allows you to conduct deeper analysis to better understand user behavior for a specific action. For example, a 'Song Added to Playlist' event could have 'Artist' and 'Playlist' as the properties. Properties are sent as key-value pairs where the key is the property name and the value is the property value. Tell me more about properties.

Use the + sign to add properties to this event.

If you add more tags, conversation must have all of them for this trigger to fire.

Please enter custom field name to the left input field as you see in the the Help Scout application. The right side should contain value, again as you see it in the Help Scout application. Both input fields are case insensitive. If you enter more custom fields, conversation must match all of them for this trigger to fire.

Filter conversations by tag. Please note: if a matching tag is present, this trigger will fire every time tags are updated on a conversation. If you add more than one tag, the conversation must have all of them for this trigger to run.

Please enter custom field name to the left input field as you see in the the Help Scout application. The right side should contain value, again as you see it in the Help Scout application. Both input fields are case insensitive. If you enter more custom fields, conversation must match all of them for this trigger to fire.

Customer can be defined either via email or via ID. One of the fields must be set.

ID of the customer. To be used together with Find Customer search or Create Customer action. Either this Customer ID or email must be defined..

Email of the customer. Either this email or customer ID must be defined..

User who is sending the reply thus only applicable for reply and draft thread types.

Select type of the thread. Not all types are equal, only reply, draft and customer can have cc and bcc.

Reply sends email to customer (unless the imported flag is used), all the other types are from the customer.

The conversation text. You can use HTML markup.

When set, the conversation will not cause external effects - it won't send emails and notifications.

Triggers Auto Reply feature if it's enabled.

Conversation ID of the conversation you are replying to. You can use Find Conversation to get the conversation ID or get the ID from a different source (New Conversation trigger for example).

ID of the customer you're replying to. If you used Find Conversation before to lookup the conversation, you can now set the Customer ID as a custom value. You can also use Find Customer step to resolve the customer by ID. The dropdown shows several recent customers and should only be used a last resort when you'r replying to a predefined static customer ID.

Text of the note. You can use HTML markup.

User who is sending the reply. The user must be authorized to access the mailbox where the conversation in question exists, otherwise error will be returned.

If set, the reply won't be sent to the user and a draft reply will be created instead.