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 .

Select the status to watch.

Who will this email be sent to? You can add multiple email addresses.

Who should be cc'd on this email? You can add multiple email addresses.

Who should be bcc'd on this email? You can add multiple email addresses.

Name of the sender from which the emails will be sent.

Email of the sender from which the emails will be sent.

Name in reply to.

Email address in reply to.

Subject of the message.

HTML body of the message (Mandatory if 'Text Content' is not passed).

Plain Text body of the message (Mandatory if 'HTML Content' is not passed. Note that 'Text Content' will be ignored if 'HTML Content' is passed).

Enter an absolute URL or select a value from a previous step in your Zap to pass the absolute URL of your attachment (it cannot be a local file). For example, https://attachment.domain.com/myAttachmentFromUrl.jpg. Format allowed: xlsx, xls, ods, docx, docm, doc, csv, pdf, txt, gif, jpg, jpeg, png, tif, tiff, rtf, bmp, cgm, css, shtml, html, htm, zip, xml, ppt, pptx, tar, ez, ics, mobi, msg, pub, eps and odt.

File attachment. Select form previous step "File (exists but not shown)"

Tag your emails to find them more easily.

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.

Select the SendinBlue list to watch.

The email address of contact that is added.

Select the list(s) to which your contact will be added.

Add - an existing SendinBlue contact will remain in all SendinBlue list(s) that they were already in and be added to the list(s) selected above. Reassign - an existing SendinBlue contact will be removed from all SendinBlue list(s) they were in and be added to the list(s) selected above.

Map your attributes. In the left column, type the name of your Brevo (formerly Sendinblue) attribute in uppercase (Attributes have to be created in your Brevo (formerly Sendinblue) account beforehand). In the right column, map them with the attributes of your trigger app. If you map the date type of attribute value, be sure to modify date to format "YYYY-MM-DD" by using Zapier Formatter step (https://zapier.com/help/create/format/modify-date-formats-in-zaps). For Brevo (formerly Sendinblue) SMS field, the expected format is +33xxxxxxxxx). For boolean type attributes, you can use "true" or "false" as string, 0 or 1 as numbers or real Boolean values.

API docs for Sendinblue are located here https://apidocs.sendinblue.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.