<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Krishna Dalal on Medium]]></title>
        <description><![CDATA[Stories by Krishna Dalal on Medium]]></description>
        <link>https://medium.com/@kdalal?source=rss-2e931ea9031------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*v_zV3IIGXhXtZ9r3.jpg</url>
            <title>Stories by Krishna Dalal on Medium</title>
            <link>https://medium.com/@kdalal?source=rss-2e931ea9031------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:31:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kdalal/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Zendesk SDKs — an in-depth guide]]></title>
            <link>https://medium.com/zendesk-developer-blog/zendesk-sdks-an-in-depth-guide-af8f837b5136?source=rss-2e931ea9031------2</link>
            <guid isPermaLink="false">https://medium.com/p/af8f837b5136</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[mobile-sdks]]></category>
            <category><![CDATA[zendesk]]></category>
            <dc:creator><![CDATA[Krishna Dalal]]></dc:creator>
            <pubDate>Wed, 16 Jun 2021 21:41:10 GMT</pubDate>
            <atom:updated>2021-06-16T21:41:10.065Z</atom:updated>
            <content:encoded><![CDATA[<h3>Zendesk SDKs — an in-depth guide</h3><p>Zendesk offers you several ways to implement our functionality onto your website or mobile apps. By using our SDKs, you can easily add messaging, ticketing, knowledge base access, live chat, and talk across your sites and applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F8CWkDhJC4MQK_U8" /></figure><p>At Zendesk, we’ve categorized our SDKs into two buckets, Zendesk SDKs for messaging and Classic SDKs.</p><p><a href="https://developer.zendesk.com/documentation/zendesk-sdks/">Zendesk SDK</a> for messaging is our newest offering built to bring customer support features such as messaging to your platforms. These SDKs are straightforward, easy to implement and are a good choice for any business looking to provide their customers with rich, personalized messaging experience.</p><p><a href="https://developer.zendesk.com/documentation/classic-sdks/">Classic SDKs</a> is a collection of our Zendesk SDKs, that include Support, Chat, and Unified SDKs. These SDKs are more complex to implement and provide a session-based experience that lacks the context and customization of messaging.</p><p>While Zendesk SDKs for messaging is new and the future of customer support, we understand that it may not be right for everyone, as it impacts other Zendesk features. An important fact to be noted, is that the SDKs are not interoperable, and they can not be integrated into the same applications simultaneously. One of the biggest differences between the SDKs is that the new Zendesk SDKs are asynchronous and lets your business and customers have one continuous conversation without ever losing conversation history. In this post, we’ll go in-depth about each SDKs’ benefits and features, as well as some key differences between each of them to help you decide which SDK is right for you.</p><p><strong>Lets start with our Zendesk SDK for messaging.</strong></p><p><a href="https://developer.zendesk.com/documentation/zendesk-sdks/"><strong>Zendesk SDK for messaging</strong></a></p><p>The Zendesk SDK for messaging is an out-of-the-box experience that lets you embed messaging options natively onto your mobile app or website. This SDK includes a number of benefits and features, as described in the table below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZzYezaK-cVGOg185DgAf8g.png" /></figure><p><a href="https://developer.zendesk.com/documentation/classic-sdks/"><strong>Zendesk Classic SDKs</strong></a></p><p>Zendesk offers Classic SDKs for Zendesk Suite products to deploy customer support across the web and mobile apps. In this next section, we’ll go over the benefits and features of the Support, Chat, and Unified SDKs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_YmQjVLazRo2V8NBVhqn7w.png" /></figure><p><strong>Key Differences</strong></p><p>While we see the new Zendesk SDK for messaging as the future for customer support, we recognize that the SDK isn’t currently at feature parity. Below, we’ll walk you through some of the key differences between the Zendesk SDKs for messaging and Classic SDKs to help you decide which one is right for you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rpIvWilgtz3W-kWGdWzcUw.png" /></figure><p><strong>Getting started with Zendesk SDKs</strong></p><p>Before deciding which Zendesk SDKs are right, here are few additional things to consider:</p><p>If your business currently relies on Chat and Support apps to pull in data, then our Classic SDKs might be best suited for your business. You can find more information <a href="https://developer.zendesk.com/documentation/classic-sdks/">here</a>.</p><p>If you’re considering switching from the Chat SDK to the Zendesk SDKs for messaging, make sure to check which of your Chat triggers, routing, reporting, and APIs are compatible with the new messaging experience. Read the full documentation <a href="https://support.zendesk.com/hc/en-us/articles/360057909933-How-Zendesk-messaging-impacts-Chat-beta-">here</a>.</p><p>If you are looking to enable custom, automated flow for your brand, we recommend activating FlowBuilder prior to embedding the mobile Zendesk SDKs.</p><p>You can find additional information for all our SDKs<a href="https://developer.zendesk.com/documentation"> here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af8f837b5136" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zendesk-developer-blog/zendesk-sdks-an-in-depth-guide-af8f837b5136">Zendesk SDKs — an in-depth guide</a> was originally published in <a href="https://medium.com/zendesk-developer-blog">Zendesk Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating Zendesk Tickets using events from Amazon EventBridge]]></title>
            <link>https://medium.com/zendesk-developer-blog/creating-zendesk-tickets-using-events-from-amazon-eventbridge-5e1ab407a2f0?source=rss-2e931ea9031------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e1ab407a2f0</guid>
            <dc:creator><![CDATA[Krishna Dalal]]></dc:creator>
            <pubDate>Thu, 08 Apr 2021 00:16:06 GMT</pubDate>
            <atom:updated>2021-04-27T01:10:21.964Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written by David Hall, published by Zendesk Developers</em></p><p><a href="https://aws.amazon.com/about-aws/whats-new/2021/03/amazon-eventbridge-introduces-support-for-api-destinations/">Amazon EventBridge API Destinations</a> allow you to use events from selected AWS services or SaaS partners to make API calls. EventBridge simplifies the process of authenticating with your chosen API, and transforming the event data into the payload of an API request.</p><p>In this tutorial, we will demonstrate how to use an Amazon EventBridge API Destination to automatically create a Zendesk ticket when a CloudWatch alert is triggered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CnEV4L1eGSdsYfxv" /></figure><p>This workflow could be used as part of an incident management process such as responding to events such as high CPU utilization or autoscaling. Zendesk tickets could be used to coordinate your response during the incident, or to facilitate post-incident activities such as team retrospectives or customer communications.</p><p>The tutorial will take approximately one hour to complete. It contains the following sections:</p><p><a href="https://medium.com/p/5e1ab407a2f0#cb49">Requirements</a></p><p><a href="https://medium.com/p/5e1ab407a2f0#b669">Pricing and limits</a></p><p><a href="https://medium.com/p/5e1ab407a2f0#07aa">Overview</a></p><p><a href="https://medium.com/p/5e1ab407a2f0#fc2a">Setting up a Amazon CloudWatch alarm</a></p><p><a href="https://medium.com/p/5e1ab407a2f0#1b6f">Create an EventBridge API destination</a></p><p><a href="https://medium.com/p/5e1ab407a2f0#0159">Create an EventBridge Rule</a></p><p><a href="https://medium.com/p/5e1ab407a2f0#cbe7">Test your setup</a></p><p><a href="https://medium.com/p/5e1ab407a2f0#16f8">Troubleshooting</a></p><p><a href="https://medium.com/p/5e1ab407a2f0#e03a">Next steps</a></p><p>Related information:</p><ul><li><a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destination-partners.html#api-destination-zendesk">API destination partners</a> in the Amazon EventBridge User Guide</li><li><a href="https://aws.amazon.com/blogs/compute/using-api-destinations-with-amazon-eventbridge/">Using API destinations with Amazon EventBridge</a> in the AWS Compute blog</li></ul><h3>Requirements</h3><p>To complete this tutorial, you will need the following:</p><ul><li>A Zendesk Support account</li><li>Zendesk Administrator credentials or a <a href="https://support.zendesk.com/hc/en-us/articles/226022787">Zendesk API token</a></li><li>An AWS account</li><li>An AWS role with access to EventBridge and Cloudwatch</li></ul><h3>Pricing and limits</h3><p>API requests made from EventBridge to your Zendesk account are counted against your <a href="https://developer.zendesk.com/rest_api/docs/support/usage_limits">Zendesk usage limits</a>.</p><p>You can read about <a href="https://aws.amazon.com/eventbridge/pricing/">EventBridge pricing on the AWS website</a>.</p><h3>Overview</h3><p>There are three key components you’ll need to create to make this work:</p><ul><li>A CloudWatch Alarm</li><li>An API Destination</li><li>An EventBridge Rule that links them together</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*l34z2YHsTQxyjVHU" /></figure><h3>Setting up a Amazon CloudWatch alarm</h3><p>Amazon provides some great directions <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ConsoleAlarms.html">here</a> on creating an alarm in Cloudwatch.</p><p>For the purpose of this tutorial, we suggest creating an alarm on a non-essential service such as the number of notifications passing through SNS topic, or the number of invocations of a Lambda function.</p><p>This will allow you to test your alarm without the need to overload or disable infrastructure. Once you’ve got the hang of how API destinations work, it’ll be a simple matter to create some real alarms that monitor your production systems.</p><p>For instance, if you’ve already worked through <a href="https://develop.zendesk.com/hc/en-us/articles/360043298894">our tutorial on using EventBridge to publish Zendesk ticket events via SNS notifications</a>, you could monitor the number of times that SNS topic gets notifications. Then test easily by creating a few fake tickets in your Zendesk account.</p><p>In this example below we’ve set an alarm to trigger if our SNS topic sends more than two notifications in a minute:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sK5W-8McKe3wU4dP" /></figure><p>As part of creating the alarm, set up an email notification so you can easily verify that your Cloudwatch alarm is triggering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1019/0*Wvu9vQlKlpqGv0C8" /></figure><p>Once you’ve created your alarm, verify that it is working by triggering the alarm condition and checking you receive the email notification.</p><h3>Create an EventBridge API destination</h3><p>Now that we have an alarm that can create alarm events, it’s time to set up the API destination in EventBridge.</p><p>The API destination allows you to:</p><ul><li>Determine which API endpoint requests should go to</li><li>Set the method to use in the request (POST, GET, DELETE etc)</li><li>Throttle the number of requests per second, to avoid negatively impacting API limits</li><li>Define the authentication method for requests and securely store credentials</li></ul><p>To create the API destination:</p><ol><li>In your AWS account, open the <a href="https://console.aws.amazon.com/events">EventBridge console</a>.</li><li>In the left navigation pane, choose <strong>API destinations</strong>.</li><li>Scroll down to the API destinations table, then choose <strong>Create API destination</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rfPaQlTt9a15-1nI" /></figure><p>Complete the details for the API destination. The names and descriptions your use in this section can be tailored to suit your needs, but pay close attention to the following settings:</p><p><strong>API destination endpoint</strong>: <a href="https://your_zendesk_subdomain.zendesk.com/api/v2/tickets">https://YOUR_ZENDESK_SUBDOMAIN.zendesk.com/api/v2/tickets</a><br>(<em>replace YOUR_ZENDESK_SUBDOMAIN with your own subdomain</em>)</p><p><strong>HTTP method</strong>: POST</p><p><strong>Invocation rate limit per second</strong>: 1</p><p><strong>Connection: </strong>Create a new connection</p><ul><li><strong>Authorization type: </strong>Basic (Username/Password)</li><li><strong>Username: </strong>your Zendesk Administrator username (email address)</li><li><strong>Password:</strong> your Zendesk Administrator password<br>(<em>note: if you would prefer to use a Zendesk API token to authenticate, see “next steps” at the end of this tutorial</em>)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/0*lwzlMHUT3nd10kGc" /></figure><h3>Create an EventBridge Rule</h3><p>Now that we have the API destination set up, next we need an EventBridge rule that will filter the types of events we want to listed for, and associate the CloudWatch alarm events with the API Destination you just created.</p><p>To create the Rule:</p><ol><li>In the left navigation pane, choose <strong>Rules</strong></li><li>Make sure the “<strong>default</strong>” Event bus is selected.</li><li>Click “<strong>Create rule</strong>”</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tDAd3S_Z2GJRkEiZ" /></figure><p>First we need to define an Event pattern. The pattern does two important things:</p><ul><li>It determines which event source to listen for (i.e. which AWS service, in our case CloudWatch)</li><li>It further refines which events should be routed on to our API destination (in our case, Alarm State Change events where the state becomes “ALARM”)</li></ul><p><strong>Event pattern</strong></p><ul><li>select <strong>custom pattern</strong></li><li>Select <strong>Edit</strong></li><li>Add the following JSON into the text box</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zn7V-fM_ejcufMO30XxxNQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/0*kq9OremoIFriqp0F" /></figure><p>Next, we need to select the Target, which is where events that match our Pattern criteria will be sent (i.e. in our case, the API destination we created).</p><p>To set up the Targe:</p><p><strong>Target</strong></p><ul><li>Select<strong> API destination</strong></li><li>Select <strong>Use an existing API destination</strong></li><li>Select the destination <strong>you created in the previous step</strong></li><li><strong>API destination endpoint </strong>and<strong> Connection </strong>will be populated automatically based on the setting you created in the previous step</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/0*RkXSipFXVENX6oWE" /></figure><p>It is important to add a header parameter, so that the Zendesk API will understand the request:</p><p><strong>Header parameters</strong></p><p>Add a parameter with the <strong>Key</strong> Content-Type and <strong>Value</strong> application/json</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/0*A3VJg5x3WX0oWEtk" /></figure><p>Next we use the Input transformer to define how we would like the incoming event payload to be transformed into the outgoing API request. This has two parts:</p><ul><li>The Input Path, which assigns “placeholder” names to elements of the incoming event</li><li>The Input Template, which uses a mix of plain text and those placeholders to define the outgoing payload.</li></ul><p>When an event passes through the Input Transformer, the placeholders will be populated with the corresponding values from the incoming event.</p><p>To set up the Input Transformer:</p><p>Click <strong>Configure Input</strong> to expand this section</p><ul><li>select <strong>Input transformer</strong></li></ul><p><strong>Input Path</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GoqadfmzhPS163WyuPOGEQ.png" /></figure><p><strong>Input Template</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cy5DAWT4bC6nhQEX5zHVQA.png" /></figure><p>Select<strong> Create a new role for this specific resource</strong>.</p><p>This will create a narrowly-scoped role that lets EventBridge use the API destination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/0*VC8pemEIO6tDK6bC" /></figure><p>Select <strong>Create</strong> at the bottom of the page to finish creating your Rule.</p><h3>Test your setup</h3><p>Now that you have all the parts in place, it’s time to test your work.</p><p>Trigger your CloudWatch alarm, and after a moment your should see a new ticket created in your Zendesk instance:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/0*B0wX0pcbpEkzznrm" /></figure><h3>Troubleshooting</h3><p>If your setup doesn’t work the first time, try checking the following:</p><p>Zendesk authentication in the Connection:</p><ul><li>If you’re using basic authentication, make sure the Zendesk user is active, and has sufficient permissions to create a ticket via the Zendesk APIs</li><li>If you’re using API key authentication, make sure the API key haven’t expired or been revoked</li><li>If you’re using an API token to authenticate the Connection, make sure you’ve <a href="https://support.zendesk.com/hc/en-us/articles/115000510267?page=2#heading2">base64 encoded the right information</a></li></ul><p>The API destination:</p><ul><li>Make sure you’ve included the Content-Type header</li><li>Check that the API destination Status is Active. If you are troubleshooting an authentication issue, too many successive failures can cause the destination to become De-authorized</li><li>You can read more here about <a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destinations.html#eb-api-destination-error-codes">error codes</a> for API destinations</li><li>You can read more here about <a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destinations.html#eb-api-destination-error-codes">how retries work</a> for API destinations</li></ul><p>EventBridge settings:</p><ul><li>Make sure you’ve created the EventBridge Rule on your default bus, not a Partner bus.</li><li>Check that the Pattern and Input Transformer settings match the details provided above.</li></ul><p>CloudWatch:</p><ul><li>Check that your CloudWatch alarm is triggering correctly by looking for the email notification. Note that CloudWatch alarms can sometimes take several minutes to return to the OK state after being in ALARM.</li></ul><h3>Next steps</h3><p>Now that you’ve got a basic alarm working, you’ll probably want to tailor this to suit your real-world requirements.</p><p>Tighten up security by using an API key rather than your username &amp; password to authenticate the connection.</p><ul><li><a href="https://support.zendesk.com/hc/en-us/articles/226022787-Generating-a-new-API-token-">Generating a Zendesk API token</a></li><li><a href="https://support.zendesk.com/hc/en-us/articles/115000510267?page=2#heading2">Authenticating using a Zendesk API token</a> involves creating a base64 encoded version of the string your_email_address/token:your_api_token</li><li>In your AWS account, open the <a href="https://console.aws.amazon.com/events">EventBridge console</a></li><li>In the left navigation pane, choose <strong>API destinations</strong></li><li>In the API destinations table, select the <strong>Connections</strong> tab</li><li>Click on the <strong>Connection name</strong> that you created earlier</li><li>Select <strong>Edit</strong></li><li>Change the <strong>Authorization type</strong> to API Key</li><li>API key name Authorization</li><li>Value Basic your_base64_encoded_string<br>(e.g. something like Basic ZmFrZW1haWxAaGFwcHl0b290aHBhc3RlLmNyZy90b2tlbjpoODk3ZzRoODk3NGcyYml1ZzI0YmlvZzI0b2cyNG9nMjRvYml=)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/0*14tLpLXsLKMePzCh" /></figure><h4>Modify the alarm source, or the way the events create Zendesk tickets</h4><ul><li>Learn more about <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ConsoleAlarms.html">setting up CloudWatch alarms</a>.</li><li>Learn more about <a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-event-patterns-content-based-filtering.html">using event Patterns to determine which events are routed</a> to your API destination.</li><li>Learn more about <a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-transforming-target-input.html">using the Input Transformer</a> to craft your ticket API request.</li></ul><p>You could also consider how else this pattern might be used to integrate AWS services or other SaaS systems with your Zendesk account:</p><ul><li>Learn about the other <a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-service-event.html">AWS services that can send events into EventBridge</a>.</li><li>Learn about <a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-saas.html">SaaS systems that can send events into EventBridge</a>.</li><li>Learn about the <a href="https://developer.zendesk.com/rest_api/docs/zendesk-apis/resources">various Zendesk APIs</a> you could send requests to.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e1ab407a2f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zendesk-developer-blog/creating-zendesk-tickets-using-events-from-amazon-eventbridge-5e1ab407a2f0">Creating Zendesk Tickets using events from Amazon EventBridge</a> was originally published in <a href="https://medium.com/zendesk-developer-blog">Zendesk Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Add Messaging to your React Native App]]></title>
            <link>https://medium.com/zendesk-developer-blog/add-messaging-to-your-react-native-app-e7c460035df4?source=rss-2e931ea9031------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7c460035df4</guid>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[tutorial]]></category>
            <dc:creator><![CDATA[Krishna Dalal]]></dc:creator>
            <pubDate>Fri, 05 Mar 2021 01:17:50 GMT</pubDate>
            <atom:updated>2021-03-05T01:17:50.866Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written by Andrew Hughes, published by Zendesk Developers</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/69162b776f5065e1448ca83551b79803/href">https://medium.com/media/69162b776f5065e1448ca83551b79803/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7c460035df4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zendesk-developer-blog/add-messaging-to-your-react-native-app-e7c460035df4">Add Messaging to your React Native App</a> was originally published in <a href="https://medium.com/zendesk-developer-blog">Zendesk Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enable Proactive Notifications using WhatsApp and Zendesk]]></title>
            <link>https://medium.com/zendesk-developer-blog/enable-proactive-notifications-using-whatsapp-and-zendesk-3e2268bbf763?source=rss-2e931ea9031------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e2268bbf763</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[messaging-apis]]></category>
            <category><![CDATA[whatsapp]]></category>
            <dc:creator><![CDATA[Krishna Dalal]]></dc:creator>
            <pubDate>Fri, 06 Nov 2020 19:42:16 GMT</pubDate>
            <atom:updated>2020-11-06T19:42:16.800Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*XVGIC9wuF4JwiNHWxDhwcQ.png" /></figure><p><em>Written by Chris Green, published by Zendesk Developers</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6ef3db1dbd2258a2326a1a998ed02a18/href">https://medium.com/media/6ef3db1dbd2258a2326a1a998ed02a18/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e2268bbf763" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zendesk-developer-blog/enable-proactive-notifications-using-whatsapp-and-zendesk-3e2268bbf763">Enable Proactive Notifications using WhatsApp and Zendesk</a> was originally published in <a href="https://medium.com/zendesk-developer-blog">Zendesk Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Developer Webinar] Learn how to scale your CX apps using messaging on September 1]]></title>
            <link>https://medium.com/zendesk-developer-blog/developer-webinar-learn-how-to-scale-your-cx-apps-using-messaging-on-september-1-466bf74b2e15?source=rss-2e931ea9031------2</link>
            <guid isPermaLink="false">https://medium.com/p/466bf74b2e15</guid>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[webinar]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Krishna Dalal]]></dc:creator>
            <pubDate>Thu, 20 Aug 2020 22:39:11 GMT</pubDate>
            <atom:updated>2020-08-20T22:39:11.609Z</atom:updated>
            <content:encoded><![CDATA[<p>As customer service becomes increasingly digital-first in the new normal, it’s important to build digital experiences that can help you scale. In this developer webinar, we’ll show you 3 ways to scale your CX apps using messaging. Plus, we’ll cover the benefits of messaging vs. chat, advanced messaging use cases, demos and a live Q&amp;A with our messaging experts.</p><p><a href="https://www.zendesk.com/support/webinars/?D2C=2531375&amp;partnerref=slack&amp;utm_source=internal&amp;utm_medium=organic&amp;utm_campaign=webinar">Join us</a> on September 1st to learn how to:</p><ul><li>Easily implement a chatbot solution across multiple channels</li><li>Drive rich CX engagement with full contextual support through proactive messaging</li><li>Streamline product questions, delivery updates and more with external collaboration</li></ul><p><a href="https://www.zendesk.com/support/webinars/?D2C=2531375&amp;partnerref=slack&amp;utm_source=internal&amp;utm_medium=organic&amp;utm_campaign=webinar">Sign up now!</a></p><p>If you are unable to join us on September 1, register anyway and we’ll make sure the recording gets to your inbox.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=466bf74b2e15" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zendesk-developer-blog/developer-webinar-learn-how-to-scale-your-cx-apps-using-messaging-on-september-1-466bf74b2e15">[Developer Webinar] Learn how to scale your CX apps using messaging on September 1</a> was originally published in <a href="https://medium.com/zendesk-developer-blog">Zendesk Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visualize your Data in Zendesk Sunshine]]></title>
            <link>https://medium.com/zendesk-developer-blog/visualize-your-data-in-zendesk-sunshine-8f0b9b71f52e?source=rss-2e931ea9031------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f0b9b71f52e</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[tutorial]]></category>
            <dc:creator><![CDATA[Krishna Dalal]]></dc:creator>
            <pubDate>Fri, 12 Jun 2020 15:56:17 GMT</pubDate>
            <atom:updated>2020-06-12T20:24:38.820Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written by Swaathi Kakarla, published by Zendesk Developers</em></p><p>Delivering an exceptional customer experience is a critical part of building trust and brand loyalty. And in this new normal, customer support agents are overwhelmed with the influx of tickets, so every bit of context that they can get about their customers can help differentiate a support experience.</p><p>The Zendesk Sunshine platform connects all your customer data in one place using Profiles, Events and Custom Objects, giving you greater insights into your customers. In this tutorial, we’ll show you how to build a custom application using the Zendesk Agent Framework (ZAF) that sits within the Zendesk agent workspace.</p><p>These apps can be as contextual as needed since they have direct access to the page or ticket the user is currently viewing. ZAF apps are basically iframe applications, so they can be built with any client or server side languages. They can also be included in a number of <a href="https://developer.zendesk.com/apps/docs/developer-guide/setup#setting-the-app-location">locations</a>, including the apps sidebar, ticket editor, navbar, and sidebar for full page applications.</p><p>Here’s what a sidebar app looks like build with ZAF:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4vaA21XB9v4NWFGr" /></figure><p>The image above shows that the app sits on the sidebar and pulls in context from the page currently being viewed. The app is able to pull out information like ticket ID, requester ID, and using <a href="https://developerblog.zendesk.com/using-custom-objects-in-zendesk-sunshine-cf2e82f57756">Sunshine Custom Objects</a>, related customer data related to the requester. Developers can use this information and show data that is relevant to agents.</p><p>Now let’s see how to build your first ZAF app with ReactJS!</p><h3>Here’s what you need to get started</h3><ul><li>Zendesk Support plan, <a href="https://develop.zendesk.com/hc/en-us/articles/360000036968">get started with a free trial</a></li><li>Basic understanding of APIs</li><li>Working knowledge of Javascript, HTML and CSS</li></ul><h3>How does it work?</h3><p>When building a ZAF application there are two important files: the manifest file and the ZAF SDK.</p><p><strong>1. Manifest File</strong></p><p>The manifest.json file is a config file that specifies where the app will render in the <a href="https://support.zendesk.com/hc/en-us/articles/360024218473-About-the-Zendesk-Agent-Workspace">Zendesk agent workspace</a>; you can choose from any of <a href="https://developer.zendesk.com/apps/docs/developer-guide/setup#setting-the-app-location">5 app locations within the file</a>. It also specifies the location of the iframe HTML file within the app folder.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2e8a2f62910cb1d2463d4e233f137bf0/href">https://medium.com/media/2e8a2f62910cb1d2463d4e233f137bf0/href</a></iframe><p>Technically, this is all you need to build a ZAF app. It can be built using any client-side or server-side technology, including open source libraries like React.js. If you only use client-side technologies like HTML, JavaScript, and CSS, you can let Zendesk host the app. If you prefer using server-side technologies, you can host the app on a remote server.</p><p>However, if you’d like to interact with framework APIs, you must use the ZAF SDK.</p><p><strong>2. ZAF SDK</strong></p><p>The <a href="https://developer.zendesk.com/apps/docs/developer-guide/using_sdk">ZAF SDK</a> gives you access to the ZAF client that lets your app communicate with the host, Zendesk agent workspace. You can import the SDK to your code base by including the following snippet of Javascript code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/96470b50c21613b102efbbeb5268bc4e/href">https://medium.com/media/96470b50c21613b102efbbeb5268bc4e/href</a></iframe><p>Here’s an example of how you can use the ZAF client to fetch the ticket requester, typically the name of a customer who files the ticket:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d2479c5f4ba0ef66a32af0ef52e40d28/href">https://medium.com/media/d2479c5f4ba0ef66a32af0ef52e40d28/href</a></iframe><p>You can read more about the SDK feature set <a href="https://developer.zendesk.com/apps/docs/developer-guide/using_sdk#working-with-framework-apis">here</a>.</p><h3>Installing and using the Zendesk Apps Tools</h3><p>In order to create a ZAF app, you will need a ZAT server to host it (during development).</p><p>To <a href="https://develop.zendesk.com/hc/en-us/articles/360001075048-Installing-and-using-the-Zendesk-apps-tools#topic_wxt_wqm_1l">install the ZAT server</a>, you will need to have <a href="https://www.ruby-lang.org/en/documentation/installation/">Ruby 2.1 or above installed</a>.</p><p>Open the command line / Terminal on your development machine and type in:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7471331ba62ef710fbe1a9fbec231d30/href">https://medium.com/media/7471331ba62ef710fbe1a9fbec231d30/href</a></iframe><p><strong><em>Note:</em></strong> If you’re using macOS or Ubuntu and any of the following commands give you an error message that you don’t have permission for a directory, start the command with `sudo` to request admin privileges, then enter the password for your system when promoted. Example: `$ sudo gem install rake`.</p><p>Once both the gems are installed, you can test it out by typing in, `zat`, which will also give you a list of commands supported by the apps tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0xIAycsDe3JqGs74" /></figure><p>If you did not get the above message, you will have to try installing the gems again.</p><h3>Creating A ZAF Application</h3><p>To create a ZAF application, simply type in `zat new` in a directory of your choice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qroVyeBGr3qE3YJf" /></figure><p>This will create 3 image files and the manifest.json file. It will also create the assets and translations folder.</p><p>The image files can be replaced with the logo of your app.</p><p>The image above also shows that I’ve chosen to use a file called “assets/index.html” as the starting point for my iframe application. This can be configured to your preference.</p><h3>Using ReactJS in your ZAF App</h3><p>Let’s replace the contents of the body tag in `assets/index.html` with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Aa9PBup1IviI7oYE" /></figure><p>Let’s break the HTML file down.</p><p><strong>1. Hook for React Components to render</strong></p><p>This div acts as a hook for React Components to render out into the HTML. You can identify it with anything you’d like. Here, I use the ID “sidebar_container.”</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5e9a02a112210a379cf73acda7786dc4/href">https://medium.com/media/5e9a02a112210a379cf73acda7786dc4/href</a></iframe><p><strong>2. External Scripts</strong></p><p>The next part of the HTML file imports all required JS files. Specifically, React, React DOM and the Zendesk SDK.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/567f809fb3a66f1b5c3d32455a4b4c55/href">https://medium.com/media/567f809fb3a66f1b5c3d32455a4b4c55/href</a></iframe><p><strong>3. Internal Scripts</strong></p><p>The last part of the HTML loads the internal JS file that contains the ReactJS business logic.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/344c1536592e8231f6fbe5c594c0e2d3/href">https://medium.com/media/344c1536592e8231f6fbe5c594c0e2d3/href</a></iframe><h3>Using the ZAF client</h3><p>The ZAF client can be used to extract information from the host Zendesk agent workspace. In this example, the ZAF app will be rendered in the workspace whenever a user opens a ticket.</p><p>With that context, the ZAF client is now able to retrieve the ticket ID and the user who requested it.</p><p>The ReactJS code snippet below shows how to extract the ticket requester ID.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vBhUUyUABkLlGn_V" /></figure><p>The code above uses the ZAF client to get the ticket data and passes the requesterID on to a function that retrieves all <a href="https://develop.zendesk.com/hc/en-us/articles/360043990774-Accessing-Sunshine-events-in-Zendesk-apps">events</a> associated with the user.</p><p>Now let’s see how to render out those events to the iframe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dl2b5Qsm5NTOTndS" /></figure><p>This will render out events and their attributes in HTML with relevant tags.</p><p>Finally, the entire React component needs to be mounted to the iframe, using the snippet below,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t407BXR9HW9LYdkc" /></figure><p>You can see that the DOM element used as a hook here, is the `sidebar_container` ID. This is present in the `assets/index.html` file.</p><h3>Testing the ZAF App</h3><p>To test your ZAF iframe app, you can start the ZAT server and then visit any ticket page in the Zendesk workspace.</p><p>To start the ZAT server, simply type in `zat server` in your project directory:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tpL4zh-T8EMrgcuX" /></figure><p>In your favorite browser, navigate to any ticket in Zendesk Support. The URL should look something like this: <a href="https://subdomain.zendesk.com/agent/tickets/321"><em>https://subdomain.zendesk.com/agent/tickets/321</em></a><em>.</em> Simply append `?zat=true` to the end of the URL. Like this: <a href="https://subdomain.zendesk.com/agent/tickets/321?zat=true"><em>https://subdomain.zendesk.com/agent/tickets/321?zat=true</em></a>.</p><p>If you’re using Chrome or Firefox and now see a shield icon in the Address bar, click the shield icon and agree to load an unsafe script (Chrome) or to disable protection on the page (Firefox). If you don’t do this, the browser will block your app from being loaded into Zendesk Support. <em>Ensure that you do this either in a Chrome or Firefox browser. Safari does not support loading unsafe scripts.</em></p><p>Finally, click on the “Apps” button on the top right corner of the page. This will load any ZAT apps to the browser. If not, click on the “Reload all apps” button just below it on the open panel to the right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pJnlcKVlcqGpAkqf" /></figure><p>This will load any ZAF apps to the sidebar. If you need to debug, simply toggle the Web Inspector.</p><p>To read a more detailed tutorial on starting your ZAT server and executing scripts, visit this link, <a href="https://develop.zendesk.com/hc/en-us/articles/360001075048">Installing and using the Zendesk apps tools</a>.</p><h3>Validating and Packaging the ZAF App</h3><p>Once you’re done developing your application, you need to package it and upload it to the Zendesk App Market. The first step toward that is validating your app.</p><p>To validate the ZAF application, simply type in `zat validate`:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/0*120ERsXBFDClFvIN" /></figure><p>To package the ZAF application, simply type in `zat package`:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NgXMYEn5yvorFJaA" /></figure><p>This creates a ZIP file in your tmp directory. This is what needs to be uploaded to your Zendesk instance and/or published to the <a href="https://developer.zendesk.com/apps/docs/publish/partner_program_intro">Zendesk marketplace</a>.</p><h3>Uploading and installing the app in Zendesk Support</h3><p>Finally! You’re now ready to upload your application to your instance of Zendesk Support. Now, you can use your ZAF app without having to host it locally. The ZAF app will be hosted by Zendesk itself.</p><p>Let’s take a look at the steps to achieve that.</p><ol><li>In <a href="https://www.zendesk.com/login/?utm_source=google&amp;utm_medium=Search-Paid&amp;utm_network=g&amp;utm_campaign=SE_AW_AM_US_EN_N_Sup_Brand_TM_Alpha_D_H&amp;matchtype=e&amp;utm_term=zendesk%20support&amp;utm_content=403581403163&amp;utm_adgroup=&amp;gclsrc=aw.ds&amp;&amp;gclid=EAIaIQobChMImcDwxbm06QIV_z6tBh1UJQFjEAAYASABEgInyvD_BwE">Zendesk Support</a>, click the Admin icon (gear icon) in the sidebar, then select Manage from the Apps category.</li></ol><p>2. Click Upload Private App in the upper-right corner of the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q3LyT5UTaKU2Tbsl" /></figure><p>3. Enter the name of your app.</p><p>4. Click Choose File and select the zip file of your app.</p><p>5. Click Upload to upload the app to Zendesk Support, then again after reading the risks and limitations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CSWEZayTieBMDvk7" /></figure><p>6. When prompted, click Install.</p><p>And voila! If all goes well, your ZAF application will be online.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Kg2HYOIhdXwdpLmg" /></figure><p>You can find all the ReactJS code used to build this app on <a href="https://github.com/swaathi/zaf">this Github link</a>.</p><h3>Continue your Journey</h3><p>Building a contextual app within the Zendesk Agent workspace, allows you to gain additional insights into your customers while building better relationships.</p><p>Check out these additional developer resources to learn more:</p><p><a href="https://developerblog.zendesk.com/using-custom-objects-in-zendesk-sunshine-cf2e82f57756">Using Custom Objects in Zendesk Sunshine</a></p><p><a href="https://developer.zendesk.com/apps/docs/developer-guide/getting_started">Zendesk Apps Developer Guide</a></p><p><a href="https://develop.zendesk.com/hc/en-us/articles/360002124307-What-is-the-Sunshine-API-">What is the Sunshine API?</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f0b9b71f52e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zendesk-developer-blog/visualize-your-data-in-zendesk-sunshine-8f0b9b71f52e">Visualize your Data in Zendesk Sunshine</a> was originally published in <a href="https://medium.com/zendesk-developer-blog">Zendesk Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learn How to Integrate Data into Zendesk Sunshine]]></title>
            <link>https://medium.com/zendesk-developer-blog/learn-how-to-integrate-data-into-zendesk-sunshine-1c9e8bc537f3?source=rss-2e931ea9031------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c9e8bc537f3</guid>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[sunshine]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Krishna Dalal]]></dc:creator>
            <pubDate>Fri, 05 Jun 2020 23:48:19 GMT</pubDate>
            <atom:updated>2020-06-05T23:48:19.811Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written by Andrew Hughes, published by Zendesk Developers</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd589d8752416e50d9b2c2543296bc75/href">https://medium.com/media/dd589d8752416e50d9b2c2543296bc75/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c9e8bc537f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zendesk-developer-blog/learn-how-to-integrate-data-into-zendesk-sunshine-1c9e8bc537f3">Learn How to Integrate Data into Zendesk Sunshine</a> was originally published in <a href="https://medium.com/zendesk-developer-blog">Zendesk Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Custom Objects in Zendesk Sunshine]]></title>
            <link>https://medium.com/zendesk-developer-blog/using-custom-objects-in-zendesk-sunshine-cf2e82f57756?source=rss-2e931ea9031------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf2e82f57756</guid>
            <category><![CDATA[custom-object]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[zendesk]]></category>
            <dc:creator><![CDATA[Krishna Dalal]]></dc:creator>
            <pubDate>Fri, 08 May 2020 17:53:24 GMT</pubDate>
            <atom:updated>2020-05-08T17:53:24.817Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written by Scott Fitzpatrick, published by Zendesk Developers</em></p><p>Data can be extremely valuable in helping provide context in customer service interactions. Take for example relevant data in context about a customer’s recent order, products, or subscription plan information that an agent can use to quickly resolve an issue.</p><p>Think of the last time you called customer support about a product’s warranty, and how frustrating it was to go from agent to agent, trying to solve your issue. Sunshine Custom Objects helps avoid this scenario by connecting the product to the customer, creating a seamless experience.</p><p>Enter Sunshine Custom Objects — Zendesk’s database-as-a-service offering made available through the Zendesk Sunshine platform. Sunshine Custom Objects was designed specifically for storing structured data about a customer’s relationship with a business and surfacing this data within the Zendesk Support agent workspace. Below, I will provide step-by-step instructions on how to set up custom objects to model and store any kind of business data.</p><h3>Introducing Custom Objects</h3><p>Every type of customer service software includes the concept of a ticket, conversation, or a user. But most software doesn’t capture the concept of a product, order, or other business data related to the customer interaction — at least out of the box. With Custom Objects in Zendesk Sunshine, you can model and store proprietary business data within a customizable schema and data model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y62XVPo31zh8VJ50" /></figure><h3>Here’s what you need to get started</h3><ul><li>Zendesk Support Enterprise, <a href="https://develop.zendesk.com/hc/en-us/articles/360000036968">get started with a free trial</a></li><li>Zendesk Sunshine Lite or above (this is included with Support Enterprise)</li><li>Basic understanding of data modeling</li><li><a href="https://www.zendesk.com/resources/sunshine-platform-use-cases/">Use case for Custom Objects</a></li><li><a href="https://docs.google.com/spreadsheets/d/1Y5_OO4P6d16-HZW3P61gnDZipAAeLotMB2ANpgOG32g/edit?usp=sharing">Simple data set</a></li></ul><p><strong>Here’s what you’ll do</strong></p><ol><li>Identify the need for customer context beyond ticket and user fields, such as product details, warranty information, contract terms, order details, or otherwise.</li><li>Find the data source and take a sample extract of the data to use for this tutorial. Use <a href="https://docs.google.com/spreadsheets/d/1Y5_OO4P6d16-HZW3P61gnDZipAAeLotMB2ANpgOG32g/edit#gid=0">this sample data set</a> with Product details for a quick-start.</li><li>Using the <a href="https://support.zendesk.com/hc/en-us/articles/360037716253-Sunshine-custom-objects-guide-for-non-developers#topic_fk5_wyl_mjb">Sunshine Admin Center</a>, create a Custom Object type to define the properties of your data. For example, if you want to store Products, properties would include SKU number, color, and category. If your data was a spreadsheet, these would be the column headers.</li><li>Again, using the Sunshine Admin Center, create a <a href="https://developer.zendesk.com/rest_api/docs/sunshine/relationship_types">Custom Relationship Type</a> to link your new Custom Object Type to a User in Zendesk Support.</li></ol><h3>The step-by-step guide</h3><p>Let’s assume you’ve identified your data set and use case. Let’s walk through the process of configuring Custom Objects (Steps 3 and 4 above).</p><p>Start by navigating to the <a href="https://support.zendesk.com/hc/en-us/articles/360037716253-Sunshine-custom-objects-guide-for-non-developers#topic_fk5_wyl_mjb">Sunshine Admin Center</a>, found under Admin &gt; Settings in Zendesk Support. Here you will find a point-and-click interface for creating Custom Object types, Custom Relationship types, as well as managing <a href="https://develop.zendesk.com/hc/en-us/articles/360042942754-Getting-started-with-Sunshine-events">Events </a>and <a href="https://develop.zendesk.com/hc/en-us/articles/360042606474-Getting-started-with-Sunshine-profiles">Profiles</a> that appear in the <a href="https://support.zendesk.com/hc/en-us/articles/360024218473-About-the-Zendesk-Agent-Workspace">Agent Workspace.</a></p><p>In this example, we want to store product data and relate it back to users on a Zendesk Support ticket. So we’ll first need to define the Products Custom Object Type.</p><p>From within Sunshine, there is a link to <a href="https://z3n-developer.zendesk.com/admin/sunshine/objects/types">Custom Object Types</a> and a button to “Add Object Type.” Upon clicking on the button, you are brought to a screen allowing you to define an object type with relevant properties. In this particular example, I have defined an object type called Product with the following properties:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/0*-giPyQms6zgshdJO" /></figure><p>Upon saving, the next step is to create relationship types to represent the following:</p><ul><li>Many:Many — Product:User (needs to be done through the creation of a One:Many relationship between Product:User and a One:Many relationship between User:Product)</li><li>One:Many — Product:Ticket</li></ul><p>As seen in the above screenshot of the Sunshine UI, a link to Relationship Types is available directly below Object Types. After navigating to this page, a very similar process is followed to create the above relationship types. See the screenshots below representing the creation of the above relationship types:</p><p>User:Product (one-to-many) relationship — first half of many-to-many implementation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/0*r7x9JK8TxbNxdN-1" /></figure><p>Product:User (one-to-many) relationship — second half of many-to-many implementation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OCJEKw3t5VbhfwTP" /></figure><p>Product:Ticket (one to many) relationship</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/933/0*fM8tLATb4KiHeN4O" /></figure><h3>Continue your Sunshine Journey</h3><p>Regardless of your particular business use case, Sunshine Custom Objects can have a positive impact.</p><p>This post highlighted how to get successfully up and running with Sunshine Custom Objects, however the journey doesn’t stop there. Check out these additional resources to learn more:</p><p><a href="https://develop.zendesk.com/hc/en-us/articles/360002073807-Custom-objects-handbook">Sunshine Custom Objects Handbook</a></p><p><a href="https://develop.zendesk.com/hc/en-us/articles/360042606474-Getting-started-with-Sunshine-profiles">Getting Started with Sunshine Profiles</a></p><p><a href="https://develop.zendesk.com/hc/en-us/articles/360042942754-Getting-started-with-Sunshine-events">Getting Started with Sunshine Events</a></p><p>To get the latest developer updates and resources, join our <a href="https://www.zendesk.com/developers/?_ga=2.139636215.534711297.1586293351-511229567.1585340833#contact-form-modal">developer community</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*2-URgdq4CQaJpW8l" /></figure><p>Scott Fitzpatrick is a Fixate IO Contributor and has 7 years of experience in software development. He has worked with many languages and frameworks, including Java, ColdFusion, HTML/CSS, JavaScript and SQL.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf2e82f57756" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zendesk-developer-blog/using-custom-objects-in-zendesk-sunshine-cf2e82f57756">Using Custom Objects in Zendesk Sunshine</a> was originally published in <a href="https://medium.com/zendesk-developer-blog">Zendesk Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>