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

Query results must have a unique id field so we can deduplicate records properly! Otherwise we will make a best guess. You must also include desired ordering and limiting in the query.

Note: This query must run in less than 30 seconds and it is recommended that you return no more than 5,000 rows

Usually something auto-incremented like id. Must be unique. Column names that contain a space must be enclosed within brackets [ ].

Usually something like date_updated or last_modified. This should ideally be a datetime column that is set to the current datetime whenever a row is updated.

Trigger on changes to cells in this column only. Leave blank if you want to trigger on changes to cells in all columns.

You should include desired ordering and limiting (usually to 1 record) in the query.

This query must run in less than ~30 seconds.

Only teams that have the Zapier app installed from the Teams Store can be used.

Mentions of this member will trigger the zap. Make sure to specify a value for a member and/or a highlight word. Specifying both a member and a highlight word means that both the member and word need to be included in a message to trigger the zap.

Mentions of this word will trigger the zap. Case insensitive. Make sure to specify a value for a highlight word and/or a member. Specifying both a member and a highlight word means that both the member and word need to be included in a message to trigger the zap.

Only teams that have the Zapier app installed from the Teams Store can be used.

Only teams that have the Zapier app installed from the Teams Store can be used.

To mention team members, put their display name, email, or userID between “at” tags. For example, you could use <at>Jane Doe</at>, <at>jane.doe@example.com</at>, or <at>jane-doe-user-id</at> to mention a team member "Jane Doe".

API docs for Microsoft Teams are located here https://docs.microsoft.com/en-us/graph/teams-concept-overview

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.

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?

We expect at least one unique (and usually autoincrement) primary key column so we can deduplicate records properly! Otherwise we will make a best guess on a random column to use to deduplicate.

Highly recommended! Usually you want the results to be most recent first so we can skim off only new results, so choose something like date_created or your autoincrement id. Column names that contain a space must be enclosed within brackets [ ].

We default to what the primary key is on the table as the unique key to deduplicate on. If you prefer another field, select it here.

Specify the chat to trigger for new messages.

If true, new messages by you will be excluded. Select false to trigger on any new messages - including those by you.

Only teams that have the Zapier app installed from the Teams Store can be used.

Only teams that have the Zapier app installed from the Teams Store can be used.