Step 1: Create an extension and add a link handler

• After successfully logging into Cliq, hover over the top right corner and click on your profile. Then navigate to Bots & Tools > My Extensions.
  
• On the right side, click the Create Extension button.
  
• To learn more about extensions and their purposes, refer to the Introduction to Extensions.
  
• Create an extension using your preferred name. Please specify the following details: the extension name, a description (to help users understand the extension's purpose), and an image to identify it.
  
• Under the link handlers section, enter github.com to configure the extension to preview links for that domain.
  
• Bundle the newly created form function - addCommentPullRequest, as it is mandatory to include at least one component to an extension, and then click Create.
  

Step 2: Configuring the preview handler

• After creating an extension, a popup will appear that provides an overview, which includes information about the extension. It will also list the connectors, showing the components bundled with the extension and their associated app keys.
  
• Additionally, handlers will allow you to configure access, customize settings, and manage links within the extension.
  
• Navigate to handlers, scroll down, and under link handlers, hover over to preview handler.
  

• The Preview Handler expands a rich response when a URL is shared in a conversation. Click edit code and copy and paste the script below.
  

Step 3: Configuring the action handler

• We have refined the response of the pull request URL when it is shared in a Cliq conversation. Now, we need to define the actions to be performed when the buttons in the unfurled response are clicked.
  
• This can be configured in the action handler. To locate it, navigate to the extension handlers. Scroll down to find the link handlers section, then hover over to the action handler.
  
• The action handler executes actions when the buttons in the unfurled card are clicked. Click "Edit Code" and copy and paste the script below.
  

Step 4: Handling the form submit handler to add comments to a pull request

• When clicking the "Add a comment" button, a form will be triggered to allow users to add comments in the specified multi-line input text field. This form should be submitted using the form functions in Cliq.
  
• To create this function, navigate to Bots & Tools > Functions. On the right side, click "Create Function" and name the function "addCommentPullRequest." Choose the Function Type as "Form."
  
• After that, click "Save & Edit Code" and paste the script provided below. 

1. response = Map();
2. formValues = form.get("values");
3. pullRequest_ID = formValues.get("pullRequest_ID");
4. repositoryName = formValues.get("repositoryName");
5. owner = formValues.get("owner");
6. comment = formValues.get("comment");
7. params = Map();
8. params.put("body",comment);
9. params.put("event","COMMENT");
10. headers = Map();
11. headers.put("Content-Type","application/json");
12. addComment = invokeurl
13. [
14. url :"https://api.github.com/repos/" + owner + "/" + repositoryName.getSuffix("/") + "/pulls/" + pullRequest_ID + "/reviews"
15. type :POST
16. parameters:params + ""
17. headers:headers
18. detailed:true
19. connection:"githubforcliq"
20. ];
21. info addComment;
22. responseCode = addComment.get("responseCode");
23. if(responseCode == 200)
24. {
25. banner = {"text":"Comment added to the pull request","status":"success","type":"banner"};
26. return banner;
27. }
28. else
29. {
30. banner = {"text":"Unable to add review comments!","status":"failure","type":"banner"};
31. return banner;
32. }
33. return Map(); 
    

Note :

You need to configure the app link to get a rich, unfurled response for the GitHub PR links posted in any chat. Refer to the link below to configure the unfurl link in Zoho Cliq.

How can you configure link unfurling in Zoho Cliq?  

🔄 Workflow explanation  

💼 Business benefits  

• Faster review cycles – Reduces turnaround time by bringing PRs directly into team conversations.
  
• Improved code quality – Promotes timely feedback from key collaborators and senior reviewers.
  
• Increased developer visibility – Ensures pull requests don’t go unnoticed or remain idle.
  
• Streamlined collaboration – Centralizes communication around code changes, reducing context-switching.