If left blank, we'll trigger on every tag.

The name of the event that occurred. This is presented to your App’s admins when filtering and creating segments. For example, updated-plan.

Limited to max 5 key/value pairs.

Select a company to tag. You can also select Custom Value from the dropdown to search for a company by the Company ID.

You can also select Custom Value from the dropdown and add a tag name. If a tag with a matching name doesn't exist, a new one will be created automatically.

If Yes is selected, the tag will be removed from the Company.

Specify the user you would like to tag or untag.

You can also select Custom Value from the dropdown and add a tag name. If a tag with a matching name doesn't exist, a new one will be created automatically.

If Yes is selected, the tag will be removed from the User.

The "ID" value from a previous search step. If no ID is provided, a new Lead will be created. (Note: this is different from the "user_id" value).

The email you want to assign to the lead.

The phone number you want to assign the lead.

If you want the current datetime to be used, try entering "now".

An ip address (e.g. “1.2.3.4”) representing the last ip address the user visited your application from. (Used for updating location_data).

Key/value pairs containing any other data about the user you want Intercom to store.

Field names must not contain Periods (‘.’) or Dollar (‘$’) characters. .

Key/value pairs containing any other data about the user you want Intercom to store.

If you want the current datetime to be used, try entering "now".

A unique string identifier for the user.

An ip address (e.g. “1.2.3.4”) representing the last ip address the user visited your application from. (Used for updating location_data).

API docs for Intercom are located here https://developers.intercom.com/reference

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.

Which value would you like to search by? You can use an ID, Email, or User ID (which returns the most recent result).

Put your desired search value here. (e.g. If it's an email, make sure the Search Mode is set to email).

Enter the name of the company you're trying to find.

How much revenue the company generates for your business each month.

The name of the plan you have associated with the company.

Key/value pairs containing any other data about the user you want Intercom to store.

Field names must not contain Periods (‘.’) or Dollar (‘$’) characters.

Which value would you like to search by? You can use an ID, Email, or User ID (which returns the most recent result).

Put your desired search value here. (e.g. If it's an email, make sure the Search Mode is set to email).

The "ID" value from a previous search step. If no ID is provided, a new Lead will be created. (Note: this is different from the "user_id" value).

The email you want to assign to the lead.

The phone number you want to assign the lead.

If you want the current datetime to be used, try entering "now".

An ip address (e.g. “1.2.3.4”) representing the last ip address the user visited your application from. (Used for updating location_data).

Key/value pairs containing any other data about the user you want Intercom to store.

Field names must not contain Periods (‘.’) or Dollar (‘$’) characters. .

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.

The email address of the user you wish to add a note to.

Specify the lead you would like to tag or untag.

Attach a tag to a specific lead.

If Yes is selected, the tag will be removed from the Lead.

How much revenue the company generates for your business each month.

The name of the plan you have associated with the company.

Key/value pairs containing any other data about the user you want Intercom to store.

Field names must not contain Periods (‘.’) or Dollar (‘$’) characters.

We will use this email and the User ID below, if provided, to look up the user in Intercom.io and update information from the fields below. If both email and User ID are provided, both must match an existing record for it to be found. If the user does not exist yet, we will create the user.

A unique string identifier for the user. If provided, used as part of the search for existing users. If the User ID does not match the existing record with the email address specified above, a new user record will be created.

Associates the user with a company in Intercom.

The phone number of the user.

If you want the current datetime to be used, try entering "now".

An ip address (e.g. “1.2.3.4”) representing the last ip address the user visited your application from. (Used for updating location_data).

Key/value pairs containing any other data about the user you want Intercom to store.

Field names must not contain Periods (‘.’) or Dollar (‘$’) characters.

Determines which App Extensions will appear in the dropdown below.

Which value would you like to search by? You can use the company Name or Company ID (which returns the most recent result).

Put your desired search value here. (e.g. If it's the company name, make sure the Search Mode is set to name)..

Which value would you like to search by? You can use an Email, ID, or User ID (which returns the most recent result).

Put your desired search value here. (e.g. If it's an email, make sure the Search Mode is set to email).

Which value would you like to search by? You can use the company Name or Company ID (which returns the most recent result).

Put your desired search value here. (e.g. If it's the company name, make sure the Search Mode is set to name)..

How much revenue the company generates for your business each month.

The name of the plan you have associated with the company.

Key/value pairs containing any other data about the user you want Intercom to store.

Field names must not contain Periods (‘.’) or Dollar (‘$’) characters.

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.