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.

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.

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.

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.

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.