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).

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.

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.

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.

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

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.

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. .

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.