Account to which the lead need to be merged.

If set to true Account name of the above selected Account will be replaced by the Company name.

Contact to which the lead need to be merged.

User ID to which the new contact/account ownership to be assigned.

Select the module you want to update an entry in.

Select the layout you want to use to update the entry with.

Entry ID to update

Choose the triggers related to this entry which needs to be executed

API docs for Zoho CRM are located here https://www.zoho.com/crm/developer/docs/api/v2/

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.

Select the layout you want to use to create a contact with.

If "yes", we will trigger any further workflows, approvals, or blueprints inside Zoho. If "no", we will not.

Connection should be of 'Administrator' privilege to fetch all entries in the module, otherwise the entries owned by respective users will only be returned.

Choose the triggers related to this entry which needs to be executed

Choose the ticket to watch for activity (audits). Shows recent tickets.

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.

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.

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?

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?

Choose the triggers related to this entry which needs to be executed

Connection should be of 'Administrator' privilege to fetch all entries in the module, otherwise the entries owned by respective users will only be returned.

Select the layout you want to use to create a lead with.

If "yes", we will trigger any further workflows, approvals, or blueprints inside Zoho. If "no", we will not.

You will need to create a descending by ID "view" in Zendesk with no grouping and select it here. Click here to learn more!

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

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.

Choose which user to update. Looked up by ID.

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?

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