<?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 Jones Zachariah Noel N on Medium]]></title>
        <description><![CDATA[Stories by Jones Zachariah Noel N on Medium]]></description>
        <link>https://medium.com/@joneszachariah.noeln?source=rss-e852fe22ab1e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fBFiZF9wwTRjGQqe1oOp3Q.jpeg</url>
            <title>Stories by Jones Zachariah Noel N on Medium</title>
            <link>https://medium.com/@joneszachariah.noeln?source=rss-e852fe22ab1e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:42:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joneszachariah.noeln/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[A Guide to understanding Freshworks integrations with Amazon EventBridge]]></title>
            <link>https://medium.com/freshworks-developer-blog/a-guide-to-understanding-freshworks-integrations-with-amazon-eventbridge-9782e54f1076?source=rss-e852fe22ab1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9782e54f1076</guid>
            <category><![CDATA[freshworks-developer]]></category>
            <category><![CDATA[freshworks-intergrations]]></category>
            <category><![CDATA[amazon-eventbridge]]></category>
            <category><![CDATA[freshworks-product-events]]></category>
            <category><![CDATA[freshworks]]></category>
            <dc:creator><![CDATA[Jones Zachariah Noel N]]></dc:creator>
            <pubDate>Wed, 09 Aug 2023 06:17:48 GMT</pubDate>
            <atom:updated>2023-08-09T06:17:48.123Z</atom:updated>
            <content:encoded><![CDATA[<p>The Freshworks Developer portal provides developers like you with tools, resources, and documentation to build custom applications and integrations with Freshworks products. And, as you build apps on the Freshworks Developer portal, it is important to think about you can optimize the processing of event payloads while you solve complex business problems. The Freshworks customer you are building for may require you to even build the integration with their existing infrastructure.</p><p>One effective way to achieve this is by using middleware or a computation engine, which can help streamline data flow and improve overall efficiency. By adopting a middleware or computation engine approach, you could provide your customers the flexibility they need to integrate with their preferred infrastructure.</p><p>Some of the popular use cases where this approach helps with:</p><ul><li>Enabling data synchronization between Freshworks products and other systems.</li><li>Building data-driven analytical dashboards using data from Freshworks products to provide detailed insights and facilitate custom dashboards.</li><li>Automating workflows based on the ticket/conversation in real time whenever there is a respective action on the Freshworks’ product end.</li><li>Enhancing the agent experience with sentiment analysis.</li><li>Archiving and logging data for governance purposes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9aIx0w4Jx6kTeECzVLe-sg.png" /></figure><p>As an app developer, integrating with <a href="https://aws.amazon.com/eventbridge/">Amazon EventBridge</a> can provide you with a highly efficient way to capture and process product events on your app. And, the pre-existing schema of (all) event payloads in the Amazon EventBridge Schema Registry, makes the entire process becomes much more streamlined and effortless.</p><p>In this blog, you will learn about integrating with Amazon EventBridge, from setting up the integration to understanding how to process them on AWS, with the help of an example.</p><h3>Setting up Amazon EventBridge integration</h3><p>Assuming you already have an AWS account, follow these steps to set up integration between Freshworks and Amazon EventBridge:</p><p><strong>Step 1</strong>: Open the <a href="https://www.freshworks.com/apps/">Freshworks Marketplace</a> and search for <strong>Amazon Eventbridge</strong>, which is available for integration with Freshdesk, Freshsales Classic, and Freshsales Suite. Select your preferred product, and click <strong>Install</strong>.</p><p><strong>Step 2</strong>: On the app’s <strong>Configuration</strong> page, follow these instructions::</p><ul><li>In the <strong>AWS Account ID</strong> field, enter your AWS account ID.</li><li>In the <strong>Events</strong> field, select the event the app which should publish to your SaaS event bus on Amazon EventBridge.</li><li>In the <strong>Region</strong> field, enter the AWS Region.</li><li>After configuring the values, the page should resemble the image below.</li></ul><figure><img alt="Amazon EventBridge app configuration page in Freshdesk" src="https://cdn-images-1.medium.com/max/1024/0*BwtBGq5nx2LCsvCX" /><figcaption><em>Amazon EventBridge app configuration page in Freshdesk</em></figcaption></figure><p><strong>Step 3</strong>: Click <strong>Save</strong> to save the changes.</p><p>To verify if the integration is successful, navigate to your AWS Console and go to <strong>Amazon EventBridge</strong> &gt; <strong>Integration</strong> &gt;<strong> Partner event sources</strong>. You can now see a list of newly created SaaS Event buses and can view their details.</p><figure><img alt="Freshworks created a SaaS Event bus on Amazon EventBridge" src="https://cdn-images-1.medium.com/max/1024/0*hQomTjTCBmjX1X6a" /><figcaption><em>Freshworks created a SaaS Event bus on Amazon EventBridge</em></figcaption></figure><p>Your SaaS Event bus has been created in your AWS account, allowing Freshworks to publish events to this specific bus.</p><h3>Understanding the flow of execution</h3><figure><img alt="Freshworks product events flow and integration with Amazon EventBridge" src="https://cdn-images-1.medium.com/max/691/0*WE35yJSIzpqIMhtF" /><figcaption><em>Freshworks product events flow and integration with Amazon EventBridge</em></figcaption></figure><p>After setting up the integration, let’s take action to generate the subscribed events.</p><p>For instance, consider that the app is installed on your Freshdesk instance, and it is subscribed to the onTicketCreate and onTicketUpdate events.</p><p>When a new ticket is created, irrespective of source, it triggers an event called onTicketCreate. The app is subscribed to this event and utilizes it. Subsequently, Freshworks publishes this event and its associated data as a payload to the SaaS Event bus on your AWS Account. The payload contains information about the ticket, including details about the person who created it and the person who requested it as a JSON object.</p><pre>{<br>  &quot;version&quot;: &quot;0&quot;,<br>  &quot;id&quot;: &quot;7c3ce57a-8224-361e-a89f&quot;,<br>  &quot;detail-type&quot;: &quot;onTicketUpdate&quot;,<br>  &quot;source&quot;: &quot;aws.partner/freshworks.com/1054665/freshdesk&quot;,<br>  &quot;account&quot;: &quot;1234567890&quot;,<br>  &quot;time&quot;: &quot;2023-03-27T22:59:41Z&quot;,<br>  &quot;region&quot;: &quot;us-east-1&quot;,<br>  &quot;resources&quot;: [],<br>  &quot;detail&quot;: {<br>    &quot;meta&quot;: {<br>      &quot;timestamp&quot;: 1679957981.1268516<br>    },<br>    &quot;ticket&quot;: {}<br>  }<br>}</pre><p><em>A sample event payload structure</em>.</p><p>After publishing an event to the SaaS Event bus, you can use Amazon EventBridge’s event rules to easily filter and route the event to your desired AWS product destination for data ingestion.</p><p>While most use cases would require downstream events to be sent to your AWS resources, it is also possible to use Amazon EventBridge API destinations to make HTTP API requests to Freshdesk or any other HTTP endpoints. This would enable bi-directional integrations.</p><h3>Analyzing the sentiment of Freshdesk tickets</h3><p>With an understanding of how to set up the integration and how it works, let’s look at how integrating with Freshdesk events can help you analyze the sentiment of Freshdesk tickets.</p><figure><img alt="Architecture diagram of taking Freshworks events and analyzing sentiment using Step Functions, Amazon EventBridge, and API Destinations." src="https://cdn-images-1.medium.com/max/996/0*8ZoWQSKHs9PeUKqL" /><figcaption><em>Architecture diagram of taking Freshworks events and analyzing sentiment using Step Functions, Amazon EventBridge, and API Destinations.</em></figcaption></figure><p>When a new ticket is created, it triggers the onTicketCreate event, which is then published to the SaaS Event bus. An event rule is configured to activate a Step Function that runs the DetectSentitment action on Amazon Comprehend using the ticket description. This reveals whether the ticket description is positive, negative, or mixed, along with the percentile of each sentiment.</p><p>If the state machine executes successfully and determines the sentiment, an event is published to the Event bus. An API destination is configured to use the <a href="https://developer.freshdesk.com/api/#update_ticket">Freshdesk update ticket API</a>, which updates the ticket’s priority and constructs the payload for the HTTP API request to Freshdesk.</p><pre>{ <br>  &quot;priority&quot;:4<br>}</pre><p>Let’s say, a new ticket is created on Freshdesk with no priority assigned to it. Then, the system will automatically assign a default priority of “low” to it, as shown in the following image:</p><figure><img alt="Freshdesk ticket with low priority" src="https://cdn-images-1.medium.com/max/1024/0*mqUAp7Ff6BszROfB" /><figcaption><em>Freshdesk ticket with low priority</em></figcaption></figure><p>Now that the integration is in place and all executions have been completed successfully, the ticket priority is updated based on the sentiment analysis of the ticket description, as shown in the following image:</p><figure><img alt="Updated Freshdesk ticket with priority" src="https://cdn-images-1.medium.com/max/1024/0*1QdV2pG9Tc7FI1Ko" /><figcaption><em>Updated Freshdesk ticket with priority</em></figcaption></figure><p>In this blog, we went through the steps to integrate Amazon EventBridge with Freshworks and were able to understand its use case.</p><p>By understanding how to integrate Freshworks product events with Amazon EventBridge, we can not only facilitate the flow of downstream events into your middleware and enhance your workloads but also establish a bi-directional flow of data. We can apply similar methods to ingest and work with events from Freshworks, similar to the process followed with ticket sentiment analysis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9782e54f1076" width="1" height="1" alt=""><hr><p><a href="https://medium.com/freshworks-developer-blog/a-guide-to-understanding-freshworks-integrations-with-amazon-eventbridge-9782e54f1076">A Guide to understanding Freshworks integrations with Amazon EventBridge</a> was originally published in <a href="https://medium.com/freshworks-developer-blog">Freshworks Developer Platform Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>