{"id":2223,"date":"2026-05-15T10:00:00","date_gmt":"2026-05-15T10:00:00","guid":{"rendered":"https:\/\/aaxonix.com\/resources\/?p=2223"},"modified":"2026-04-11T18:45:11","modified_gmt":"2026-04-11T18:45:11","slug":"zoho-cliq-github-integration","status":"publish","type":"post","link":"https:\/\/aaxonix.com\/resources\/zoho-cliq-github-integration\/","title":{"rendered":"Zoho Cliq and GitHub Integration: Developer Notifications and PR Alerts in Chat"},"content":{"rendered":"<style>\n.aax-post{font-family:'Poppins',sans-serif;color:#1a2332;max-width:820px;margin:0 auto;line-height:1.75}\n.aax-post h2{font-size:1.55rem;font-weight:600;margin:2.5rem 0 .9rem;color:#0a1628}\n.aax-post h3{font-size:1.15rem;font-weight:600;margin:1.8rem 0 .6rem;color:#1a2332}\n.aax-post p{margin:0 0 1.1rem}\n.aax-post ul,.aax-post ol{margin:0 0 1.1rem;padding-left:1.5rem}\n.aax-post li{margin-bottom:.45rem}\n.aax-post table{width:100%;border-collapse:collapse;margin:1.5rem 0;font-size:.93rem}\n.aax-post th{background:#0a1628;color:#fff;padding:.6rem 1rem;text-align:left}\n.aax-post td{padding:.55rem 1rem;border-bottom:1px solid #e8edf4}\n.aax-post tr:nth-child(even) td{background:#f5f7fb}\n.aax-post .faq-section{background:#f5f7fb;border-radius:10px;padding:1.8rem 2rem;margin:2.5rem 0}\n.aax-post .faq-item{margin-bottom:1.2rem;border-bottom:1px solid #e0e6ef;padding-bottom:1.2rem}\n.aax-post .faq-item:last-child{border-bottom:none;margin-bottom:0;padding-bottom:0}\n.aax-post .faq-question{font-weight:600;color:#0a1628;margin-bottom:.5rem}\n.aax-post .faq-answer{color:#3a4a5c;line-height:1.65}\n.aax-post .aax-cta{background:linear-gradient(135deg,#0a1628 0%,#1a3a5c 100%);border-radius:12px;padding:1.8rem 2rem;margin:2.5rem 0;text-align:center}\n.aax-post .aax-cta p{color:#e8edf4;margin:0 0 1.2rem;font-size:1.05rem}\n.aax-post .aax-cta a{display:inline-block;background:#fff;color:#0a1628;font-weight:600;padding:.65rem 1.6rem;border-radius:6px;text-decoration:none;font-size:.95rem}\n<\/style>\n<div class=\"sp-toc-wrap\"><nav class=\"sp-blog-toc\" id=\"spBlogToc\" style=\"display:none\">\n  <h4><svg width=\"14\" height=\"14\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><line x1=\"8\" y1=\"6\" x2=\"21\" y2=\"6\"\/><line x1=\"8\" y1=\"12\" x2=\"21\" y2=\"12\"\/><line x1=\"8\" y1=\"18\" x2=\"21\" y2=\"18\"\/><line x1=\"3\" y1=\"6\" x2=\"3.01\" y2=\"6\"\/><line x1=\"3\" y1=\"12\" x2=\"3.01\" y2=\"12\"\/><line x1=\"3\" y1=\"18\" x2=\"3.01\" y2=\"18\"\/><\/svg> On this page<\/h4>\n  <ol class=\"sp-toc-list\" id=\"spTocList\"><\/ol>\n<\/nav><\/div>\n<div class=\"aax-post\">\n\n<p>Development teams that split their attention between GitHub and a team messaging app lose minutes on every context switch. A pull request sits unreviewed for hours because the assigned reviewer never saw the notification buried in email. A CI\/CD pipeline fails on the main branch, and nobody catches it until the next developer tries to merge. Zoho Cliq and GitHub integration solves this by routing repository events, from PR reviews to deployment status updates, directly into the channels and bot conversations where your engineering team already works. This guide covers the full technical setup: configuring Cliq bots with incoming webhooks, selecting the right GitHub events, building actionable message cards, and creating slash commands that let developers interact with GitHub without leaving chat.<\/p>\n\n\n<figure style=\"margin:36px 0;text-align:center;line-height:0;\"><img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/03\/inline_zoho_cliq_github_integration_1.jpg\" alt=\"Close-up of a person coding on a laptop, showcasing web development and programming concepts.\" style=\"width:100%;max-width:820px;height:auto;border-radius:10px;box-shadow:0 4px 20px rgba(10,22,40,.13);\" loading=\"lazy\" \/><\/figure>\n<h2>Why Connect Zoho Cliq with GitHub<\/h2>\n\n<p>Most development teams already use a chat tool for standups, quick questions, and incident response. GitHub notifications, on the other hand, default to email or the GitHub web UI, both of which sit outside the primary communication flow. This disconnect creates blind spots.<\/p>\n\n<p>Connecting <a href=\"https:\/\/www.zoho.com\/cliq\/help\/platform\/bot-incomingwebhookhandler.html\" rel=\"noopener noreferrer\" target=\"_blank\">Zoho Cliq&#8217;s incoming webhook handlers<\/a> with GitHub webhooks closes that gap. PR review requests appear in a dedicated channel seconds after they are created. Build failures surface immediately, with a button that opens the failed run in one click. Issue assignments ping the right person in their Cliq DM rather than sitting in an inbox.<\/p>\n\n<p>The practical benefits for engineering teams include:<\/p>\n<ul>\n<li>Faster code review cycles because reviewers see requests in real time<\/li>\n<li>Reduced mean time to detection for broken builds<\/li>\n<li>Single-pane visibility across repositories without switching tabs<\/li>\n<li>Actionable notifications that link directly to the PR, issue, or deployment<\/li>\n<\/ul>\n\n<p>If your team already uses <a href=\"https:\/\/aaxonix.com\/resources\/zoho-cliq-team-messaging\/\" class=\"sp-content-link\">Zoho Cliq for team messaging<\/a>, adding GitHub integration is a natural next step that compounds the value of both tools.<\/p>\n\n<h2>Setting Up the Zoho Cliq Bot and Incoming Webhook<\/h2>\n\n<p>The foundation of this integration is a Cliq bot configured with an incoming webhook handler. This bot receives HTTP POST requests from GitHub and converts the raw JSON payload into formatted messages for your channels or direct conversations.<\/p>\n\n<h3>Step 1: Create a New Bot<\/h3>\n\n<p>Open Zoho Cliq and navigate to your profile picture, then select Bots and Tools. Click on Bots, then Create Bot. Give it a name like &#8220;GitHub Notify&#8221; and a description that clarifies its purpose. Save the bot to reach the handlers configuration page.<\/p>\n\n<h3>Step 2: Configure the Incoming Webhook Handler<\/h3>\n\n<p>In the bot handlers list, locate the Incoming Webhook Handler and click Edit Code. This handler fires every time an external service sends data to your bot&#8217;s webhook URL. The handler receives a parameter object containing headers and body from the incoming request. Write Deluge code that parses the GitHub event payload and returns a formatted message card.<\/p>\n\n<p>A minimal handler that posts push event details looks like this:<\/p>\n\n<pre><code>response = Map();\nbody = payload.get(\"body\");\nevent = headers.get(\"X-GitHub-Event\");\nif(event == \"push\")\n{\n    repo = body.get(\"repository\").get(\"full_name\");\n    pusher = body.get(\"pusher\").get(\"name\");\n    commits = body.get(\"commits\");\n    msg = pusher + \" pushed \" + commits.size() + \" commit(s) to \" + repo;\n    response.put(\"text\", msg);\n}\nreturn response;<\/code><\/pre>\n\n<h3>Step 3: Generate a Webhook Token<\/h3>\n\n<p>Go to Bots and Tools, then Webhook Tokens. Click Generate New Token. Cliq allows a maximum of five active tokens at any time, so plan your allocation if you run multiple integrations. Copy the token, you will append it to the webhook URL when configuring GitHub.<\/p>\n\n<p>The complete bot webhook URL follows this format: <code>https:\/\/cliq.zoho.com\/api\/v2\/bots\/github-notify\/incoming?zapikey=YOUR_TOKEN<\/code><\/p>\n\n<h2>Configuring GitHub Webhooks for Cliq<\/h2>\n\n<p>On the GitHub side, open the repository you want to connect. Navigate to Settings, then Webhooks, and click Add webhook. Paste the Cliq bot webhook URL in the Payload URL field. Set the content type to <code>application\/json<\/code>. Leave the secret field empty unless you want to implement HMAC signature verification in your Deluge handler.<\/p>\n\n<h3>Selecting the Right Events<\/h3>\n\n<p>GitHub offers over 40 <a href=\"https:\/\/docs.github.com\/en\/webhooks\/webhook-events-and-payloads\" rel=\"noopener noreferrer\" target=\"_blank\">webhook event types<\/a>. Subscribing to all of them floods your channel with noise. For a developer notification bot, these events cover the most common use cases:<\/p>\n\n<table>\n<thead>\n<tr><th>Event<\/th><th>What It Covers<\/th><th>Typical Use<\/th><\/tr>\n<\/thead>\n<tbody>\n<tr><td>pull_request<\/td><td>PR opened, closed, merged, review requested<\/td><td>Review cycle tracking<\/td><\/tr>\n<tr><td>pull_request_review<\/td><td>Review submitted (approved, changes requested)<\/td><td>Review status updates<\/td><\/tr>\n<tr><td>issues<\/td><td>Issue opened, assigned, closed, labeled<\/td><td>Bug and task tracking<\/td><\/tr>\n<tr><td>push<\/td><td>Commits pushed to any branch<\/td><td>Branch activity monitoring<\/td><\/tr>\n<tr><td>check_run \/ check_suite<\/td><td>CI\/CD build started, completed, failed<\/td><td>Build status alerts<\/td><\/tr>\n<tr><td>deployment_status<\/td><td>Deployment succeeded or failed<\/td><td>Release monitoring<\/td><\/tr>\n<tr><td>release<\/td><td>New release published<\/td><td>Version announcements<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n<p>Select &#8220;Let me select individual events&#8221; and check only the events your team actually needs. You can always add more later without recreating the webhook.<\/p>\n\n\n<figure style=\"margin:36px 0;text-align:center;line-height:0;\"><img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/03\/inline_zoho_cliq_github_integration_2.jpg\" alt=\"Man participating in video call at desktop computer in stylish office setting with greenery.\" style=\"width:100%;max-width:820px;height:auto;border-radius:10px;box-shadow:0 4px 20px rgba(10,22,40,.13);\" loading=\"lazy\" \/><\/figure>\n<h2>Building Actionable Message Cards for PR Alerts<\/h2>\n\n<p>Plain text notifications get ignored. Message cards with structured data and clickable buttons drive action. Zoho Cliq&#8217;s message card format supports titles, themed layouts, and button arrays that open URLs or invoke server-side functions.<\/p>\n\n<h3>PR Review Request Card<\/h3>\n\n<p>When a pull_request event fires with the action &#8220;review_requested&#8221;, your handler can return a card that shows the PR title, author, branch, and a button linking directly to the review page. The Deluge response structure uses the card and buttons objects:<\/p>\n\n<pre><code>response = Map();\ncard = Map();\ncard.put(\"title\", \"Review Requested: \" + pr_title);\ncard.put(\"theme\", \"modern-inline\");\nresponse.put(\"card\", card);\n\nbuttons = list();\nbtn = Map();\nbtn.put(\"label\", \"Open PR\");\nbtn.put(\"type\", \"+\");\naction = Map();\naction.put(\"type\", \"open.url\");\ndata = Map();\ndata.put(\"web\", pr_url);\naction.put(\"data\", data);\nbtn.put(\"action\", action);\nbuttons.add(btn);\nresponse.put(\"buttons\", buttons);\nreturn response;<\/code><\/pre>\n\n<p>This pattern works for any GitHub event. Change the card title and button URL based on the event type and action field in the payload.<\/p>\n\n<h3>Routing Notifications to the Right Channel<\/h3>\n\n<p>Bot messages go to the user who installed the bot by default. To post to a specific channel, use the Cliq channel webhook endpoint instead of the bot endpoint. The URL format is <code>https:\/\/cliq.zoho.com\/api\/v2\/channelsbyname\/CHANNEL_NAME\/message?zapikey=YOUR_TOKEN<\/code>. This lets you create dedicated channels like #frontend-prs, #backend-builds, or #deploys and route events based on repository or branch.<\/p>\n\n<h2>CI\/CD Build Status Notifications<\/h2>\n\n<p>Failed builds on the main branch are high-priority events. The check_run and check_suite events from GitHub Actions, CircleCI, or any CI provider that integrates with GitHub&#8217;s Checks API provide the build status payload your Cliq bot needs.<\/p>\n\n<p>When a check_run event arrives with conclusion set to &#8220;failure&#8221;, your handler should:<\/p>\n<ol>\n<li>Extract the repository name, branch, commit SHA (first 7 characters), and the check run name<\/li>\n<li>Build a message card with a red-themed alert showing the failed check details<\/li>\n<li>Add two buttons: one to open the check run URL in GitHub, and one to open the commit diff<\/li>\n<li>Post to the team&#8217;s build-alerts channel<\/li>\n<\/ol>\n\n<p>For teams managing <a href=\"https:\/\/aaxonix.com\/resources\/zoho-projects-management-guide\/\" class=\"sp-content-link\">project workflows with Zoho Projects<\/a>, you can extend this handler to create a Zoho Projects task whenever a critical build fails, ensuring the fix gets tracked alongside your sprint backlog.<\/p>\n\n<h2>Deployment Alerts and Approval Workflows<\/h2>\n\n<p>The deployment_status event fires when a GitHub deployment transitions between states: pending, in_progress, success, failure, or error. This is particularly useful for teams that use GitHub Environments with required reviewers.<\/p>\n\n<p>A deployment notification card should include the environment name (staging, production), the deployed commit reference, the deployer, and the current status. For production deployments, add a button that opens the deployment log and another that links to your monitoring dashboard.<\/p>\n\n<h3>Approval Flows with Button Functions<\/h3>\n\n<p>Zoho Cliq button functions let you go beyond simple URL links. You can create a Cliq function that calls the <a href=\"https:\/\/docs.github.com\/en\/webhooks\/about-webhooks\" rel=\"noopener noreferrer\" target=\"_blank\">GitHub API<\/a> to approve a pending deployment review. When the deployment_status event shows a &#8220;waiting&#8221; state, your handler posts a card with an &#8220;Approve Deployment&#8221; button. Clicking it invokes a Cliq function that sends a POST request to GitHub&#8217;s deployment review API, completing the approval without the developer ever opening a browser tab.<\/p>\n\n<p>This workflow is especially valuable for teams that practice continuous deployment with manual gates on production releases.<\/p>\n\n<h2>Creating Slash Commands for GitHub Queries<\/h2>\n\n<p>Notifications push information to developers. Slash commands let developers pull information on demand. Zoho Cliq supports custom slash commands that execute Deluge code and return formatted responses.<\/p>\n\n<h3>Useful Slash Commands for GitHub<\/h3>\n\n<p>Consider building these commands for your team:<\/p>\n\n<ul>\n<li><code>\/prs [repo]<\/code> fetches open pull requests for a repository using the GitHub REST API and returns them as a list with review status indicators<\/li>\n<li><code>\/issues [repo] [label]<\/code> queries open issues filtered by label, showing assignees and age<\/li>\n<li><code>\/build [repo]<\/code> checks the latest workflow run status on the default branch and returns pass\/fail with a link<\/li>\n<li><code>\/deploy [repo] [env]<\/code> lists recent deployments for an environment with their status<\/li>\n<\/ul>\n\n<p>Each command requires a GitHub personal access token stored as a Cliq connection or a secure parameter. Create the command under Bots and Tools, then Commands. Write the execution handler to call the GitHub API, parse the JSON response, and return a formatted message card.<\/p>\n\n<p>Teams that use <a href=\"https:\/\/aaxonix.com\/resources\/zoho-flow-automation-india\/\" class=\"sp-content-link\">Zoho Flow for automation workflows<\/a> can also trigger flows from slash commands, combining GitHub data with actions in other Zoho apps like creating a Zoho Projects issue from a GitHub issue summary.<\/p>\n\n<h2>Testing and Troubleshooting the Integration<\/h2>\n\n<p>Before rolling the integration out to your full team, test each event type individually. GitHub&#8217;s webhook settings page includes a &#8220;Recent Deliveries&#8221; tab that shows every payload sent, the response code from Cliq, and the response body. This is your primary debugging tool.<\/p>\n\n<h3>Common Issues and Fixes<\/h3>\n\n<table>\n<thead>\n<tr><th>Problem<\/th><th>Cause<\/th><th>Fix<\/th><\/tr>\n<\/thead>\n<tbody>\n<tr><td>Webhook shows 401 response<\/td><td>Invalid or expired Cliq token<\/td><td>Regenerate the token in Webhook Tokens and update the GitHub webhook URL<\/td><\/tr>\n<tr><td>Messages not appearing in channel<\/td><td>Bot webhook used instead of channel webhook<\/td><td>Switch to the channel webhook endpoint URL format<\/td><\/tr>\n<tr><td>Payload too large error<\/td><td>GitHub sends large diffs in push events<\/td><td>Reduce payload size by unchecking the &#8220;Send me everything&#8221; option and selecting specific events<\/td><\/tr>\n<tr><td>Handler timeout<\/td><td>Deluge code makes slow external API calls<\/td><td>Move heavy processing to an async Cliq function and return the message immediately<\/td><\/tr>\n<tr><td>Duplicate notifications<\/td><td>Multiple webhooks configured for overlapping events<\/td><td>Audit your webhook list in GitHub settings and remove duplicates<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n<p>For teams already using <a href=\"https:\/\/aaxonix.com\/resources\/zoho-crm-api-webhooks-india\/\" class=\"sp-content-link\">Zoho CRM API and webhooks<\/a>, the debugging workflow will feel familiar since the same principles of payload inspection, response code analysis, and handler logging apply.<\/p>\n\n<h3>Monitoring Webhook Health<\/h3>\n\n<p>GitHub automatically disables webhooks that return errors consistently. Check the webhook status in your repository settings weekly. Set up a simple Cliq scheduled function that pings your webhook endpoint daily and alerts you if the response is anything other than 200.<\/p>\n\n<h2>Zoho Flow vs Custom Webhooks: Which Approach to Choose<\/h2>\n\n<p>Zoho Flow offers a no-code path to connecting GitHub and Zoho Cliq. You select a trigger (new GitHub issue, new PR, new commit mention), map the fields, and Flow posts a message to your chosen Cliq channel. Setup takes under ten minutes.<\/p>\n\n<p>Custom webhooks require more upfront work but provide capabilities Flow cannot match:<\/p>\n\n<table>\n<thead>\n<tr><th>Capability<\/th><th>Zoho Flow<\/th><th>Custom Webhook Bot<\/th><\/tr>\n<\/thead>\n<tbody>\n<tr><td>Setup time<\/td><td>Under 10 minutes<\/td><td>1-3 hours<\/td><\/tr>\n<tr><td>Message formatting<\/td><td>Basic text<\/td><td>Full card layout with buttons<\/td><\/tr>\n<tr><td>Event filtering<\/td><td>Limited to Flow triggers<\/td><td>Any GitHub event, any field condition<\/td><\/tr>\n<tr><td>Actionable buttons<\/td><td>Not supported<\/td><td>Open URL, invoke function, API call<\/td><\/tr>\n<tr><td>Slash commands<\/td><td>Separate setup<\/td><td>Integrated with same bot<\/td><\/tr>\n<tr><td>Approval workflows<\/td><td>Not available<\/td><td>Full support via button functions<\/td><\/tr>\n<tr><td>Maintenance<\/td><td>Zoho-managed<\/td><td>Self-maintained Deluge code<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n<p>For small teams that need basic PR and issue notifications, Zoho Flow is the faster option. For engineering teams that want CI\/CD alerts, deployment approval workflows, and custom slash commands, the webhook bot approach gives you the control you need.<\/p>\n\n<p>For a full overview of all available options, explore our <a href=\"https:\/\/aaxonix.com\/resources\/zoho-integrations-complete-guide\/\" class=\"sp-content-link\">complete guide to Zoho integrations<\/a>.<\/p>\n<div class=\"faq-section\">\n<h2>Frequently Asked Questions<\/h2>\n<div class=\"faq-item\">\n<p class=\"faq-question\">Can Zoho Cliq receive GitHub webhook notifications without third-party tools?<\/p>\n<p class=\"faq-answer\">Yes. Zoho Cliq supports bot incoming webhook handlers natively. You create a bot in Cliq, generate a webhook token, and configure the webhook URL in your GitHub repository settings. When GitHub events fire, the payload goes directly to your Cliq bot with no middleware required. You can parse the JSON payload in a Deluge handler and format it as a message card with buttons.<\/p>\n<\/div>\n<div class=\"faq-item\">\n<p class=\"faq-question\">Which GitHub events can trigger notifications in Zoho Cliq?<\/p>\n<p class=\"faq-answer\">GitHub supports over 40 webhook event types. The most useful for Cliq notifications include pull_request (opened, merged, closed), pull_request_review, issue (opened, assigned, closed), push (commits to a branch), check_run and check_suite (CI\/CD build results), deployment_status, and release (new version published). You select which events to subscribe to when configuring the webhook in your repository settings.<\/p>\n<\/div>\n<div class=\"faq-item\">\n<p class=\"faq-question\">How do I add actionable buttons to GitHub notifications in Zoho Cliq?<\/p>\n<p class=\"faq-answer\">Use the button object in your bot incoming webhook handler response. Each button needs a label, type, and action. Set the action type to open.url with the GitHub PR or issue URL so developers can jump to the relevant page in one click. You can also use invoke.function to trigger a Cliq function that posts a comment or approves a review directly from the chat interface.<\/p>\n<\/div>\n<div class=\"faq-item\">\n<p class=\"faq-question\">Is Zoho Flow a better option than custom webhooks for GitHub and Cliq integration?<\/p>\n<p class=\"faq-answer\">Zoho Flow is simpler to set up because it requires no code. It works well for basic notification routing, such as posting a message when a new issue is created. However, custom webhooks give you full control over message formatting, button actions, and conditional logic. If you need rich message cards, CI\/CD status parsing, or deployment approval workflows, a custom bot with webhook handlers is the better choice.<\/p>\n<\/div>\n<div class=\"faq-item\">\n<p class=\"faq-question\">What is the maximum number of webhook tokens allowed in Zoho Cliq?<\/p>\n<p class=\"faq-answer\">Zoho Cliq allows a maximum of 5 active webhook tokens at any time. Each token authenticates one webhook endpoint. If you need more than 5 integrations, you can route multiple GitHub repositories through a single webhook endpoint and use the repository name in the payload to differentiate the source. Plan your token allocation across bots and channels before configuring multiple repositories.<\/p>\n<\/div>\n<\/div>\n\n<div class=\"aax-cta\">\n<p>Aaxonix builds custom Zoho Cliq integrations for development teams, connecting GitHub, CI\/CD pipelines, and project management tools into a unified notification system. Book a free consultation to get a scoped integration plan for your engineering workflow.<\/p>\n<a href=\"https:\/\/aaxonix.com\/contact\/\">Book a free consultation<\/a>\n<\/div>\n\n<p>A well-configured Zoho Cliq and GitHub integration removes the friction between code changes and team awareness. Start with the events that matter most to your team, build a clean message card format, and expand from there. The combination of incoming webhooks for push notifications and slash commands for on-demand queries gives your developers a complete GitHub interface inside the tool they already have open all day.<\/p>\n\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Connect Zoho Cliq with GitHub using webhooks to get PR reviews, issue alerts, and CI\/CD build notifications directly in your team chat.<\/p>\n","protected":false},"author":1,"featured_media":2220,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[570,571,569,128,322,140,504],"class_list":["post-2223","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-developer-tools","tag-devops","tag-github","tag-team-collaboration","tag-webhooks","tag-zoho-cliq","tag-zoho-integration"],"_links":{"self":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/2223","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/comments?post=2223"}],"version-history":[{"count":2,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/2223\/revisions"}],"predecessor-version":[{"id":2665,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/2223\/revisions\/2665"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media\/2220"}],"wp:attachment":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media?parent=2223"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/categories?post=2223"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/tags?post=2223"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}