By using this app, you hereby agree to the Google Customer Match policies available here and all other applicable policies made available by Google, which are located here.

Pick which type of object you want to watch for new items of (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly).

Pick which type of object you want to update (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

The Content Document ID of a file that has been uploaded to a library in Salesforce CRM Content or Salesforce Files

Specifies whether this file is available to all users, internal users, or shared users.

Pick the type of object you want to attach the file to (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly).

Defaults to false if left blank.

Pick the type of object if you want to attach the file to (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly).

Pick which type of object you want to create (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

Search for or select the record you'd like to update. Use Custom Value to select a record from a previous step. If using the Search, click "Refresh Fields" below to update the available input fields.

Pick which type of object you want to update (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

Search for or select the record you'd like to update. Use Custom Value to select a record from a previous step. If using the Search, click "Refresh Fields" below to update the available input fields.

API docs for Salesforce are located here https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_list.htm

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.

Pick which type of object you want to search for. You can only search for multiple records which are all the same object type.

Select the format of search results to be returned. If multiple search values are provided, the choice will be applied to each search value.

Pick which type of object you want to create (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

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 Sendinblue attribute in uppercase (Attributes have to be created in your 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 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.

This trigger works on Salesforce objects with less than 104,000 records. If the "Field Updated to" is specified, the limit applies to only the records with the value specified. Check how many records you have in your account by following the steps under Viewing Storage Usage. You can also setup a Zap with the New Outbound Message trigger to workaround this limit.

Pick which type of object you want to watch for changes on.

Select which campaign to add lead. If using the Search for this field, click "Refresh Fields" below to make sure all fields are available to you.

If using the Search for this field, click "Refresh Fields" below to make sure all fields are available to you.

Pick which type of object you want to create (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

Search for or select the lead you'd like to update. Use Custom Value to select a lead from a previous step. If using the Search, click "Refresh Fields" below to update the available input fields.

Pick which type of object you want to update (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

Search for or select the record you'd like to update. Use Custom Value to select a record from a previous step. If using the Search, click "Refresh Fields" below to update the available input fields.

Pick which type of object you want to search for.

Pick which type of object you want to search for.

Enter a SOQL WHERE clause. See our help docs for Tips and Examples.

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.