Choose a particular upsell from the list.

Choose a coupon to only trigger if that coupon was applied to this order.

Enter an affiliate ID to only trigger if the order was referred by a particular affiliate.

Choose whether this should trigger if the purchase is done in test mode, live mode, or both. Leave blank to trigger for both.

Choose which item you want to trigger this Zap for.

Enter an affiliate ID to only trigger if the order was referred by a particular affiliate.

Choose whether this should trigger if the cancellation is made in test mode, live mode, or both. Leave blank to trigger for both.

Choose which item you want to trigger this Zap for.

Enter an affiliate ID to only trigger if the order was referred by a particular affiliate.

Choose whether this should trigger if the pause is made in test mode, live mode, or both. Leave blank to trigger for both.

API docs for ThriveCart are located here https://apidocs.thrivecart.com/

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.

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.

The field will be used to filter the conversations. Please note that the search is not using an exact match - for example Work will match subject Healthy Work as well.

Matches any email in to, cc, bcc or a email of a customer associated with the conversation.

Advanced custom query as defined in the API documentation. For example modifiedAt:[NOW-1HOUR] only matches conversation modified less than hour ago. This query is not validated, if you get it wrong, it might get unexpected results - invalid query is ignored. You can add multiple conditions joined by AND or OR. Example number:1234 AND customerIds:100.

Mailbox name.

Email address of the user whose report you'd like to get.

Email address of the user whose report you'd like to get.

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.

Choose which item you want to trigger this Zap for.

Enter an affiliate ID to only trigger if the order was referred by a particular affiliate.

Choose whether this should trigger if the payment is made in test mode, live mode, or both. Leave blank to trigger for both.

Choose which item you want to trigger this Zap for.

Enter an affiliate ID to only trigger if the order was referred by a particular affiliate.

Choose whether this should trigger if the completion is made in test mode, live mode, or both. Leave blank to trigger for both.

Choose which item you want to trigger this Zap for.

Enter an affiliate ID to only trigger if the order was referred by a particular affiliate.

Choose whether this should trigger if the resume is made in test mode, live mode, or both. Leave blank to trigger for both.

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.

Customer ID for which you are updating properties. You can use Find Customer to get the customer ID or get the ID from a different source (New Customer trigger for example).

Customer's email.

User's email.

Email address of the user whose report you'd like to get.

The field will be used to filter the conversations. Please note that the search is not using an exact match - for example Work will match subject Healthy Work as well.

Matches any email in to, cc, bcc or a email of a customer associated with the conversation.

Advanced custom query as defined in the API documentation. For example modifiedAt:[NOW-1HOUR] only matches conversation modified less than hour ago. This query is not validated, if you get it wrong, it might get unexpected results - invalid query is ignored. You can add multiple conditions joined by AND or OR. Example number:1234 AND customerIds:100.

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.