Choose which ticket to update.

Choose which organization to update. Looked up by ID.

Must be unique. Zendesk does not allow duplicate organizations with the same name.

In this field you can store any details about the organization. e.g. the address

In this field you can store any notes you have about the organization.

Comma-separated list of tags you want to apply to the new organization.

Comma-separated list of domain names to automatically associated with this organization (format: "zapier.com, google.com").

A unique external id, you can use this to associate organizations to an external record.

Options: "true" or "false". End users in this organization are able to see each others tickets.

Options: "true" or "false". End users in this organization are able to see each others comments on tickets.

Write a search string to determine how we'll look up the agent in Zendesk. For more information, visit the Zendesk docs.

Write a search string to determine how we'll look up the organization in Zendesk. For more information, visit the Zendesk docs.

Write a search string to determine how we'll look up the user in Zendesk. For more information, visit the Zendesk docs.

Write a search string to determine how we'll look up the ticket in Zendesk. For more information, visit the Zendesk docs.

Note: the assignee must be in the default group (or specific group selected below) else an error will occur.

You can add emails of non-Zendesk users here as Collaborators.

Assign this ticket to a group.

To set the Requester, you must specify the Requester Name in this field AND the Requestor Email in the next field.

To set the Requester, you must specify the Requester Email in this field AND the Requestor Name in the previous field.

A comma separated list of tags.

Only available for tickets with a Type of "task."

If selected, this person will be set as the submitter of the ticket. Defaults to the Requester.

If selected, this will set the form to render for this ticket. Note: this is only applicable for Zendesk enterprise accounts.

Note: Only for Zendesk customers on plans with multi-brand support. More info here

If empty, will default to your default calendar.

How far before the event do you want us to trigger? For starter and free plans, this should be 16 minutes or more. For higher plans, 6 minutes or more.

To trigger only on new contacts in a certain folder, select a folder here. If empty, we will trigger on new contacts in the default Contacts folder.

If empty, will default to your default calendar.

If empty, a contact will be created in the default Contacts folder.

Microsoft allows a maximum of THREE email addresses when creating contacts.

Microsoft allows a maximum of TWO business phone numbers when creating contacts.

Microsoft allows a maximum of TWO home phone numbers when creating contacts.

Optionally, specify a name to file the contact under.

Leave this field blank to send from your own address. Use this field to send from a shared inbox you have access to.

A file to be attached to the email. Can be an actual file or a public URL which will be downloaded and attached. Plain text content will converted into a txt file and attached. Please note the maximum size for an attachment is 4MB.

API docs for Microsoft Outlook are located here https://docs.microsoft.com/en-us/graph/use-the-api

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.

If empty, a contact will be created in the default Contacts folder.

Microsoft allows a maximum of THREE email addresses when creating contacts.

Microsoft allows a maximum of TWO business phone numbers when creating contacts.

Microsoft allows a maximum of TWO home phone numbers when creating contacts.

Optionally, specify a name to file the contact under.

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.

Choose which ticket to update.

A list of tags to add to the ticket.

Choose which ticket to update.

Note: the assignee must be in the default group (or specific group selected below) else an error will occur.

Assign this ticket to a group.

A comma separated list of tags.

If selected, this person will be set as the submitter of the ticket. Defaults to the Requester.

Write a search string to determine how we'll look up the group in Zendesk. For more information, visit the Zendesk docs.

Write a search string to determine how we'll look up the ticket in Zendesk. For more information, visit the Zendesk docs.

Write a search string to determine how we'll look up the organization in Zendesk. For more information, visit the Zendesk docs.

Must be unique. Zendesk does not allow duplicate organizations with the same name.

In this field you can store any details about the organization. e.g. the address

In this field you can store any notes you have about the organization.

Comma-separated list of tags you want to apply to the new organization.

Comma-separated list of domain names to automatically associated with this organization (format: "zapier.com, google.com").

A unique external id, you can use this to associate organizations to an external record.

End users in this organization are able to see each others tickets.

End users in this organization are able to see each others comments on tickets.

Write a search string to determine how we'll look up the user in Zendesk. For more information, visit the Zendesk docs.

Must be unique. Zendesk does not allow duplicate users with the same email address.

In this field you can store any notes you have about the user.

Phone number for this user (format: +1 (555) 123-4567).

Comma-separated list of tags you want to apply to the new user.

Can be one of the following: "end-user", "agent", or "admin". Defaults to "end-user" if set and not one of those values.

Assign this user to an organization.

A unique external id, you can use this to associate organizations to an external record.

Specify if you know this user is who they say they are?

If empty, will default to your default calendar.

Specify a shared inbox you have access to, otherwise read emails from your own inbox.

If empty, will default to your default calendar.

Date and time of when this event starts. See this help doc for more information.

Date and time of when this event ends.

If "true", we'll ignore the time entered in the start and end time fields. For example, 2019-03-25 6pm would become 2019-03-25.

Allows HTML

A file to be attached to the email. Can be an actual file or a public URL which will be downloaded and attached. Plain text content will converted into a txt file and attached. Please note the maximum size for an attachment is 4MB.

If empty, the dropdown below will only show contacts in your top level contactFolder.

Microsoft allows a maximum of THREE email addresses when updating contacts.

Microsoft allows a maximum of TWO business phone numbers when updating contacts.

Microsoft allows a maximum of TWO home phone numbers when updating contacts.

If empty, will search for contacts in the default Contacts folder.

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.