Workflow recipe: Notifying External Email Addresses

What's my plan?

Triggers allow you to set up and automate ticket management and email notifications easily. However, sometimes you need to send an email notification to someone other than a Zendesk Support agent or requester, such as a shipping partner, a colleague in Finance who handles refunds, or an external email address to a different department or company. 

Use notify target to notify an external system about a new ticket or an important state change to a ticket. These systems include X Corp, JIRA, Salesforce, and many others. For example, when a ticket is set to urgent, you can send an SMS to your CEO or an update to X Corp, Yammer, or Flowdock. Or, when your customer creates a ticket and selects "Sales" from a drop-down field, it creates a case in Salesforce. These scenarios are possible with notify target.

This article includes two useful examples of how you can use notify target to send email notifications to external email addresses:

• Example: Email the CEO when a ticket is set to urgent
• Example: Email the Security Department when the "About" field is "Security"

This article then concludes with Useful tips when creating your own notifications.

For other uses of notify target with other systems, see Notifying external targets.

Tip: To find out more about how replies to target notifications work, see Why do replies to email-target notifications create a new ticket?

 Example: Email the CEO when a ticket is set to urgent

In our first example, we will start with an agent-initiated notification. Since the priority field can only be set by an agent, this notification can only be initiated by an agent.

To set this up, first create a target:

1. In Admin Center, click the Apps and integrations icon () in the sidebar, then select Targets > Targets.
2. Click add target.
3. Select Email target.
4. Fill in the fields, like in the example below.
5. Select Create target and click Submit.

 

Next, create a trigger:

1. In Admin Center, click the Objects and rules icon () in the sidebar, then select Business rules > Triggers.
2. Click Add trigger.
3. Fill in the conditions and actions, like in the example below.
4. Click Create.

Note: Use "Priority changed to urgent" rather than "Priority is urgent" to send only one notification in this ticket thread. Using "Priority is urgent" sends an external notification every time there's an update to the ticket.

When you are done, follow these steps to test:

1. Open an existing ticket.
2. Change the priority field to urgent.
3. Click Submit as open.
4. Reopen ticket.
5. Click on Events.
6. Notice that an email has been sent to the target.

 Example: Email the Security Department when the "About" field is "Security"

In the next example, we will create an end-user editable custom field called "About" with a "Security" option. This field will then display on the "Submit a request" form, so when an end-user selects it, a notification is sent to your Security Department. This is an example of an end-user initiated notification.

To set this up, first create a target:

1. In Admin Center, click the Apps and integrations icon () in the sidebar, then select Targets > Targets.
2. Click Add target.
3. Select Email target.
4. Fill in the fields, like in the example below.
5. Select Create target and click Submit.

 

Next, create a custom drop-down field:

1. In Admin Center, click the Objects and rules icon () in the sidebar, then select Tickets > Fields.
2. Click Add field.
3. Select Drop-down.
4. Enter About as the Display name.
5. Select Customers can edit.
6. Enter the values for the drop-down field, including one for Security.
7. Click Save.

For more information on creating custom ticket fields, see Adding custom fields to your tickets and support request form.

Then create a trigger that will notify the target:

1. In Admin Center, click the Objects and rules icon () in the sidebar, then select Business rules > Triggers.
2. Click Add trigger.
3. Fill in the conditions and actions, like in the example below.
4. Click Create.

Note: Use "Ticket is created" to send the notification only the first time the ticket is created. You can remove this condition if you want each following update to send a notification.

When you are finished, follow these steps to test:

1. Log out of your agent interface and go to the web portal.
2. Click Submit a request.
3. Select Security in the drop-down field.
4. Click Submit.
5. Log in to your agent interface.
6. Open ticket that was just created.
7. Click Events.
8. Notice that a notification was sent to your security department.

Useful tips when creating your own notifications

Now it's your turn to create your own custom notification. Here are some useful questions you can ask yourself to clarify what notification to create:

• Who do I want to notify? (Target)
• When do I want them notified? (Custom field)
• Do I want this triggered by an agent or end-user action? (Custom field restrictions)
• What information do I want to be sent in the notification? (Trigger)

Once you have clarified the notification you want to create, you're ready to start implementing. Here's a summary of the process:

1. Create a target for the email address where you want to send the notification.
2. Create a custom field to initiate the notification. Make the field editable, or it won't display on the "Submit a request" form.
3. Create a trigger to send the notification.
4. Test to make sure it works.