Supports HTML.

Supports HTML.

Defaults to yes.

You can use positive or negative numbers, like 4 or -3. The number you enter will be added to or subtracted from the current quantity.

You can use positive or negative numbers, like 4 or -3. The quantity will be set to the number you enter.

The customer to update.

Setting any tags here will replace all existing tags for this customer.

If "Yes", taxes won't be applied at checkout for this customer.

E.g. "KY" or "MI"

Country is required if the other address fields are filled.

Defaults to "no".

If "Yes", taxes won't be applied at checkout for this customer.

Product to add this variant to.

What should Shopify do when inventory is exhausted: deny sales or continue selling?

In order to trigger when emails are opened, this must be paired with a separate Zap using the Send Outbound Email action, with the Enable Read Receipts? field set to True.

To test with a live email, send an email to yourself using your Send Outbound Email action (with read receipts enabled) and open it, then test this trigger immediately for samples. If you don't need to test with live data, click Skip Test to use static test data.

This should return a list of dictionaries of content type JSON in reverse chronological order. For example: [{"id":1234},{"id":1235}]

If the returned JSON is not a list and is instead an object (maybe paginated), enter the key that contains the results. Example: "results", "items", "objects", etc... (children via dot syntax supported)

Zapier deduplicates the array we see each poll against the id key. If the id key does not exist, you should specify an alternative unique key to deduplicate off of. If neither are supplied, we fallback to looking for the shortest key with id in it otherwise we will raise an error.

If the content fetched is XML or HTML, optionally define an xpath to extract data from the content. Will trigger whenever the content at the xpath changes!

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

By default, Zapier gives you the entire payload of the webhook. If this is specified, Zapier will only grab the child key from the object(s) sent to Zapier. For example, given {"contact": {"name": "Mike"}}, add "contact" here to only return {"name": "Mike"}. Traverse more deeply nested children by using dot-separated syntax. Line item payloads will run your Zap for each instance of the child key.

We recommend not putting any query string arguments in the URL (use "Query String Params" below).

These params will be URL-encoded and appended to the URL when making the request. Note: If you specify nothing for this field, we will automatically encode and include every field from the previous step in the query string. If you don't want this, use the "Custom Request" action.

If "yes", this dumps the results directly to a key (set below) as JSON. If "no", we simulate a form.

Only used if As JSON.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

E.g. "KY" or "MI"

Country is required if the other address fields are filled.

Defaults to "no".

If "Yes", taxes won't be applied at checkout for this customer.

An email for your customer.

Only used if you select a product variant below.

Requires a Product chosen above. If you choose a variant, you can still fill in the Product Title and the Product Price to override the regular values.

To use this, please also enter a value in the "Discount - Amount" field.

The "Discount - Type" field determines how this value is used. For a fixed amount, enter 5.00 to discount $5.00. For a percentage, enter .25 to discount 25%.

Defaults to "Custom discount". For the discount to be applied, you must also enter values for Discount Type and Amount.

Extra metadata about the order, defined as key/value pairs. For example, Favorite color: Blue.

Should an order confirmation be sent to the customer?

Should a fulfillment confirmation be sent to the customer?

How do you want your inventory to update with this order? Default is "Bypass".

Where the order originated.

Can use html elements.

Comma Separated list of tags. Will replace existing.

Creates a single product variation in Shopify and assigns the price to this variation.

URL of one or more images to use for this product.

Defaults to yes.

Defaults to yes.

Product to choose the variant for.

Can use html elements.

Comma Separated list of tags.

The date and time when the product was published. This must be a date in the past. Defaults to the current date if left blank.

Creates a single product variation in Shopify and assigns the price to this variation.

What should Shopify do when inventory is exhausted: deny sales or continue selling?

URL of an image to use for this new product.

Defaults to yes.

Defaults to yes.

Customize the private email address associated with your mailbox. Be sure to use lowercase and numbers only. Just forward emails to this address to trigger this Zap. Want to receive to your own email address? Try Mailgun, IMAP, Mandrill, or Gmail instead.

Can be a comma separated list of emails. Limited to 5.

You can place HTML in here and we will send it as is. If this is plain text, we will try to convert it to some very basic HTML for greater client compatibility.

A file object to be attached to the email. Plain text content will converted into a txt file and attached. Please note, if the file is over ~10mb or so, you should explore using other email sending techniques (like Gmail or SMTP).

This will be your "display name" when sending. Want to send from your own email address? Try Mailgun, IMAP, Mandrill or Gmail apps instead.

Specify a reply address other than your own.

Can be a comma separated list of emails. Limited to 5.

Can be a comma separated list of emails. Limited to 5.

Set this to "yes" if your emails are received without line breaks or spacing.

Want to be notified when this email is opened? Set this to to True and set up a Zap using the New Read Receipt trigger.

The HTTP method we'll use to perform the request.

Any URL with a querystring will be re-encoded properly.

If yes, request data below will be overridden with the raw data from the previous step (you are still responsible for headers though, like Content-Type). Defaults to no.

Place raw data for the request here. Could be JSON, XML, etc. Nothing is parsed for you here (including extra line breaks or spaces -- everything is sent verbatim). You probably need to define a header below corresponding to your data Content-Type. Reminder: data provided in this field is completely ignored if you chose "yes" to pass-through.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.