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

API docs for WPForms are located here https://wpforms.com/?p=8374&post_type=wpforms_doc&preview=1&_ppp=857193bee8

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 no (and by default) this trigger will only fire the first time a user opens an email.

When samples are pulled in the next step for this trigger, the GROUPINGS data will be static, dummy data ("Example Group Category 1"). Use the example Group values to setup your Zap, and the data should reflect appropriately when the Zap runs.

When samples are pulled in the next step for this trigger, the GROUPINGS data will be static, dummy data ("Example Group Category 1"). Use the example Group values to setup your Zap, and the data should reflect appropriately when the Zap runs.

Examples: Conference Lead, Influencer, or Donor (Tag length is limited to 100 characters).

The email address of the subscriber you want to subscribe to this audience. Please don't type an email address in this field, instead this should use a value from a previous step in your Zap. Learn more here.

If yes, a confirmation email will be sent to the address before they appear on the chosen audience.

If no, the Zap will skip/halt this step if the subscriber exists, otherwise overwrites data sent.

Determines what changes to make to the subscriber's groups/interests.

• Add Only The group(s) specified below will be added to the subscriber's existing groups/interests.
• Replace All All of the subscriber's existing groups will be cleared, and replaced with the groups selected below.
• Replace Matching Clears any existing group selections only for the groups specified below. Learn more here.

This should be a two letter language code (ISO639-1) See here for the list of language codes.

The tag(s) to which the subscriber will be added. Tags will be added to any existing tags on existing subscribers.

The email address of the person you want to remove from this tag. Note: the email address must already be subscribed to the audience, or this will fail.

The email address of the subscriber you want to add a note to. The email address must already be subscribed to the audience.

The content of the note. Note length is limited to 1,000 characters.

Determines which App Extensions will appear in the dropdown below.

The name of the Campaign to find

The name of the Campaign to find

Select the audience you want to send the campaign to.

Select which segment or tag you want to send the campaign to. If no segment/tag is selected, the campaign will be sent to the entire audience selected above.

This snippet will appear in the inbox after the subject line.

Supports *|MERGETAGS|* for recipient name, such as *|FNAME|*, *|LNAME|*, *|FNAME|* *|LNAME|*, etc.

Select either a template or provide HTML email content, you cannot provide both. If both fields are left blank, the campaign draft will have no content.

Select either a template or provide HTML email content, you cannot provide both. If both fields are left blank, the campaign draft will have no content.

The email address of the Subscriber you want to find.

Limit your search to this specific Audience.

The email address of the subscriber you want to subscribe to this audience. Please don't type an email address in this field, instead this should use a value from a previous step in your Zap. Learn more here.

If yes, a confirmation email will be sent to the address before they appear on the chosen audience.

If no, the Zap will skip/halt this step if the subscriber exists, otherwise overwrites data sent.

Determines what changes to make to the subscriber's groups/interests.

• Add Only The group(s) specified below will be added to the subscriber's existing groups/interests.
• Replace All All of the subscriber's existing groups will be cleared, and replaced with the groups selected below.
• Replace Matching Clears any existing group selections only for the groups specified below. Learn more here.

This should be a two letter language code (ISO639-1) See here for the list of language codes.

The tag(s) to which the subscriber will be added. Tags will be added to any existing tags on existing subscribers.

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?

Determines which App Extensions will appear in the dropdown below.

Select a link from your campaign to track. It's not currently possible to trigger on all link clicks for a campaign with a single Zap.

If no (and by default) this trigger will only fire the first time a user clicks a link in your campaign.

To prevent timeout errors, please ensure the list of customers for this store does not exceed 3000.

If specified, will only trigger on orders created in this store. Otherwise, will default to all orders in your account.

To prevent timeouts, please ensure the list of subscribers in the segment/tag does not exceed 3000.

Select the audience you want to send the campaign to.

Select which segment or tag you want to send the campaign to. If no segment/tag is selected, the campaign will be sent to the entire audience selected above.

This snippet will appear in the inbox after the subject line.

Supports *|MERGETAGS|* for recipient name, such as *|FNAME|*, *|LNAME|*, *|FNAME|* *|LNAME|*, etc.

Select either a template or provide HTML email content, you cannot provide both. If both fields are left blank, the campaign draft will have no content.

Select either a template or provide HTML email content, you cannot provide both. If both fields are left blank, the campaign draft will have no content.

The email address of the subscriber for the custom event. The email address must already be subscribed to the audience.

Must be 2-30 characters in length. Note: Letters, numbers, underscores, hyphens, and any spaces between are considered valid characters. Any invalid characters will be ignored.

Additional properties for this event (e.g. "User Type: Premium", "Preferred Communication: Email", etc). Note: Letters, numbers, underscores, hyphens, and any spaces between are considered valid characters. Any invalid characters in the first column only will be ignored.

The email address of the subscriber you want to unsubscribe from this audience.

Completely delete this contact from MailChimp? (No: just unsubscribe them)

A Custom Value is typically used here to pass in the Campaign ID from a "Create Campaign" or "Find Campaign" step. Learn more

The tag to which the subscriber will be added.

The email address of the person you want to add to this segment. Note: the email address must already be subscribed to the audience, or this will fail.

API docs for Mailchimp are located here https://mailchimp.com/developer/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.

The email address of the Subscriber you want to find.

Limit your search to this specific Audience.

Examples: Conference Lead, Influencer, or Donor (Tag length is limited to 100 characters).