Select your desired organization.

Select your desired workspace.

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.

Subaccounts allow you to separate reputation, activity, reports, and quotas for different types of senders in a single Mandrill account. Learn more.

The display name for the sent email.

Choose an email recognizable to your recipients.

Comma separate for multiple recipients.

Comma separate for multiple recipients.

Comma separate for multiple recipients.

You must provide either body text or html, or both.

You must provide either body text or html, or both.

Schedule this email for a future date and time. Use our datetime transforms for relative-to-now scheduling. Note: Mandrill charges extra for this and you have to have a positive account balance.

Determines which App Extensions will appear in the dropdown below.

Comma separated text labels

Set a time for some number of minutes before the task is due.

If you want to attach this Task to a Workspace, choose the Organization that the Workspace is in.

Select a workspace to attach this new Task to (only shows Workspaces inside the Organization you picked above).

Supports only the fields of type plain text.

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.

Select whichever template you like, but remember to provide the right template content/variables!

Comma separate for multiple recipients.

Comma separate for multiple recipients.

Line separated and pipe (|) separated key, value pairs sent inserted into the template. For example, a single like key|{{field}}. Read more info here..

Very similar template variables, but as merge fields. Line separated and pipe (|) separated key, value pairs sent inserted into the template. For example, a single like key|{{field}}. Read more info here..

Schedule this email for a future date and time. Use our datetime transforms for relative-to-now scheduling. Note: Mandrill charges extra for this and you have to have a positive account balance.

Should Mandrill apply any included styling as inline rules?

API docs for Mailchimp Transactional are located here https://mandrillapp.com/api/docs/

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.