Skip to content

Commit be04e9d

Browse files
committed
screenshots and docs
1 parent c28a349 commit be04e9d

File tree

5 files changed

+72
-29
lines changed

5 files changed

+72
-29
lines changed

README.md

+72-29
Original file line numberDiff line numberDiff line change
@@ -17,14 +17,13 @@ A Zendesk App to help you generate links for agents.
1717
## Usage
1818
### Deploying from ZIP
1919

20-
To quickly install this application, navigate to the latest releases and download the attached `app-<DATE>.zip`. You can upload this to Zendesk
2120
Attached to the latest release is the `app-<DATE>.zip` asset that can be [uploaded to your Zendesk instance](https://developer.zendesk.com/documentation/apps/getting-started/uploading-and-installing-a-private-app/#uploading-and-installing-a-private-app-in-zendesk):
2221

23-
1. In Admin Center, click the Apps and integrations icon () in the sidebar, then select Apps > Zendesk Support apps.
24-
2. Click Upload App.
25-
3. Enter a Name for the app.
26-
4. Click Choose file and select the zip file for your private app.
27-
5. Click Save.
22+
1. In Admin Center, click the Apps and integrations, click Zendesk Support Apps.
23+
2. Click Upload private app.
24+
3. Enter the App Name.
25+
4. Click Choose File and select the zip file.
26+
5. Click Upload.
2827
6. In the pop-up box that appears, click Agree and upload this App.
2928
7. When prompted, click Install.
3029

@@ -38,36 +37,40 @@ Once the app is uploaded, you can Install it to the configured areas of Zendesk.
3837

3938
### Configuring the JSON Array of URLs
4039

41-
The following is an example of what can be entered into this app's settings:
40+
To configure the URL buttons, you must supply a JSON array of URLs with `title` and `url` properties. Here is an example:
4241

4342
```javascript
4443
[
45-
{
46-
"title": "First Title",
47-
"url": "http://example.com/?name={{ticket.requester.name}}"
48-
},
49-
{
50-
"title": "Second Title (with custom field)",
51-
"url": "http://example.com/?custom={{ticket.custom_field_424242}}"
52-
}
44+
{
45+
"title": "Facebook",
46+
"url": "https://www.facebook.com"
47+
},
48+
{
49+
"title": "Instagram",
50+
"url": "https://www.instagram.com"
51+
},
52+
{
53+
"title": "Twitter",
54+
"url": "https://www.twitter.com"
55+
},
56+
{
57+
"title": "LinkedIn",
58+
"url": "https://www.linkedin.com"
59+
},
60+
{
61+
"title": "TikTok",
62+
"url": "https://www.tiktok.com"
63+
}
5364
]
54-
55-
```
56-
This example will generate the following HTML inside the app:
57-
```html
58-
<ul>
59-
<li>
60-
<a href="http://example.com/?name=Phillip_J_Fry">First Title</a>
61-
</li>
62-
<li>
63-
<a href="http://example.com/?custom=customValue">Second Title (with custom field)</a>
64-
</li>
65-
</ul>
6665
```
6766

68-
### Sample Placeholders
67+
This will yield the following display:
68+
69+
![social_media_sites](./assets/screenshot-0.png)
6970

70-
Below is a list of just a few of the available object properties available as placeholders. To see the full list of fields, please see the [Zendesk Apps Reference - API Reference](https://developer.zendesk.com/api-reference/apps/introduction/). For example, you can use object properties available in [all locations](https://developer.zendesk.com/api-reference/apps/apps-support-api/all_locations/) and object properties available in the [ticket sidebar](https://developer.zendesk.com/api-reference/apps/apps-support-api/ticket_sidebar/) .
71+
### Using Zendesk Object Properties
72+
73+
Below is a list of just a few of the available object properties available as placeholders. To see the full list of fields, please see the [Zendesk Apps Reference - API Reference](https://developer.zendesk.com/api-reference/apps/introduction/). For example, you can use object properties available in [all locations](https://developer.zendesk.com/api-reference/apps/apps-support-api/all_locations/) and object properties available in the [ticket sidebar](https://developer.zendesk.com/api-reference/apps/apps-support-api/ticket_sidebar/).
7174

7275
```
7376
* {{ticket.id}}
@@ -86,7 +89,47 @@ Below is a list of just a few of the available object properties available as pl
8689
* {{currentUser.email}}
8790
```
8891

92+
Here is an example configuration of a URL button that has the email of the user:
93+
94+
```javascript
95+
[
96+
{
97+
"title": "Email User",
98+
"url": "mailto:{{ticket.requester.email}}"
99+
}
100+
]
101+
```
102+
103+
This generates the following button:
104+
105+
We can highlight this button and see the following URL:
106+
107+
![screenshot](./assets/screenshot-1.png)
108+
109+
### Using Custom Fields in URLs
110+
111+
Zendesk allows for [custom fields](https://support.zendesk.com/hc/en-us/articles/4420210121114-Using-custom-fields) to be added in various places like Users, Tickets, and Organizations for Zendesk Admins. These custom fields can be used in your URLs as well.
112+
113+
For example, let's say we use the custom field for the customer like `Issue Topic`, a drop down where they pick their issue type. When a custom field is created, you will see a column for the `Field ID` generated and you can copy it for the URL. If this object has an ID of `1234567890`, it can be used in a URL like so:
114+
115+
```javascript
116+
[
117+
{
118+
"title": "Customer Related Issues",
119+
"url": "http://example.com/issues?customer_id={{ticket.requester.id}}&issue_type={{ticket.custom_field_360371540635070}}"
120+
}
121+
]
122+
```
123+
124+
Given an issue type of "new feature", this would generate a URL with the values set:
125+
126+
![customer_related_issues](./assets/screenshot-2.png)
127+
![customer_related_issues_url](./assets/screenshot-3.png)
128+
129+
An important note here is that URLs generated by custom fields are not updated dynamically. If the custom field is on the Agent side for example and is updated, the page will need to be refreshed to update the URLs.
130+
89131
## Issues
132+
90133
To submit an issue, please follow the [available template](/.github/ISSUE_TEMPLATE.md).
91134

92135
## Contribution

assets/screenshot-0.png

40.5 KB
Loading

assets/screenshot-1.png

20.4 KB
Loading

assets/screenshot-2.png

24.4 KB
Loading

assets/screenshot-3.png

19.5 KB
Loading

0 commit comments

Comments
 (0)