{"id":7627,"date":"2026-06-13T05:08:11","date_gmt":"2026-06-13T05:08:11","guid":{"rendered":"https:\/\/www.coffee.ai\/articles\/fathom-zapier-crm-automation-2026"},"modified":"2026-06-13T05:08:11","modified_gmt":"2026-06-13T05:08:11","slug":"fathom-zapier-crm-automation-2026","status":"publish","type":"post","link":"https:\/\/www.coffee.ai\/articles\/fathom-zapier-crm-automation-2026","title":{"rendered":"Fathom Zapier CRM Automation: Complete 2026 Guide"},"content":{"rendered":"<p><em>Written by: Doug Camplejohn, CEO &amp; Co-Founder, Coffee<\/em><\/p>\n<h2>Key Takeaways for Fathom, Zapier, and Coffee<\/h2>\n<ul>\n<li>\n<p>Fathom Zapier CRM automation uses a seven-step setup with custom field mapping and ongoing maintenance to push summaries and action items into HubSpot or Salesforce.<\/p>\n<\/li>\n<li>\n<p>Common failure points include parsing errors, timing delays, and silent record drops whenever Fathom updates its output format or Zapier changes its integration points.<\/p>\n<\/li>\n<li>\n<p>Native Fathom integrations exist for both CRMs, and Zapier is still required for custom routing, multi-step workflows, or non-default schemas.<\/p>\n<\/li>\n<li>\n<p>Coffee\u2019s native agent ingests Fathom transcripts directly, structures them to your sales methodology, and writes structured CRM data without any Zapier layer.<\/p>\n<\/li>\n<li>\n<p>You can remove Zapier maintenance entirely and let an <a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/www.coffee.ai\/pricing\">intelligent agent handle every post-call CRM update automatically.<\/a><\/p>\n<\/li>\n<\/ul>\n<h2>How Fathom Zapier CRM Automation Works Today<\/h2>\n<p>Fathom&#8217;s Zapier integration exposes six triggers: New AI Summary, New Highlight, New Action Item, New Transcript, New Recording, and New Download Video. The three most useful for CRM automation are New AI Summary, New Action Item, and New Highlight. A standard setup follows these seven steps:<\/p>\n<ol>\n<li>\n<p>Connect Fathom to Zapier using your Fathom API credentials.<\/p>\n<\/li>\n<li>\n<p>Select a trigger, typically &#8220;New AI Summary&#8221; for note logging or &#8220;New Action Item&#8221; for task creation.<\/p>\n<\/li>\n<li>\n<p>Map the Fathom output fields to a staging step (Formatter or Code) to parse structured text.<\/p>\n<\/li>\n<li>\n<p>Add a search step to find the matching Contact or Deal record in your CRM by attendee email.<\/p>\n<\/li>\n<li>\n<p>Map parsed fields to CRM destination fields such as Notes, Tasks, or Engagements.<\/p>\n<\/li>\n<li>\n<p>Enable error handling and set up a Zap history alert for failed runs.<\/p>\n<\/li>\n<li>\n<p>Run the Zap in parallel with your manual process for at least one week before disabling manual entry.<\/p>\n<\/li>\n<\/ol>\n<p>Zapier provides pre-built templates that create or update HubSpot contacts from new Fathom recordings and create Salesforce meeting notes from new AI summaries, which shortens initial setup. Pre-built templates still require field-mapping customization for any non-default CRM schema, so RevOps teams should plan time for that work.<\/p>\n<h2>HubSpot Setup: Recommended Fathom-to-Field Mappings<\/h2>\n<p>Fathom\u2019s native HubSpot app syncs AI Meeting Summaries and Action Items to HubSpot. Many teams still add a Zapier layer for custom routing logic or multi-step workflows. Use the following field mappings as a baseline and pay attention to where HubSpot requires custom properties or extra configuration.<\/p>\n<table style=\"min-width: 100px\">\n<colgroup>\n<col style=\"min-width: 25px\">\n<col style=\"min-width: 25px\">\n<col style=\"min-width: 25px\">\n<col style=\"min-width: 25px\"><\/colgroup>\n<tbody>\n<tr>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Fathom Field<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>HubSpot Destination Object<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>HubSpot Field<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Notes<\/p>\n<\/th>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>AI Summary<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Engagement \/ Meeting<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Notes Body<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Associate to Contact and Deal<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Next Steps<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Engagement \/ Note<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Notes Body (appended)<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Prefix with &#8220;Next Steps:&#8221; label<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Action Items<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Task<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Task Title + Due Date<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Native Fathom app writes these directly, Zapier needed only for custom routing<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Highlight<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Contact Property<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Custom &#8220;Call Highlights&#8221; field<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Requires custom property creation in HubSpot<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Recording URL<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Engagement \/ Meeting<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Meeting Description<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Append as hyperlink<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Salesforce Setup: Recommended Fathom-to-Field Mappings<\/h2>\n<p><a target=\"_blank\" rel=\"noindex nofollow\" href=\"https:\/\/help.fathom.video\/en\/articles\/448640\">Fathom writes each action item as a separate Salesforce Task to open Opportunities and associated Contacts.<\/a> Zapier-based setups follow similar patterns and benefit from consistent mappings. Use these mappings and keep the Opportunity and Contact links consistent across every Task and Note.<\/p>\n<table style=\"min-width: 100px\">\n<colgroup>\n<col style=\"min-width: 25px\">\n<col style=\"min-width: 25px\">\n<col style=\"min-width: 25px\">\n<col style=\"min-width: 25px\"><\/colgroup>\n<tbody>\n<tr>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Fathom Field<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Salesforce Destination Object<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Salesforce Field<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Notes<\/p>\n<\/th>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>AI Summary<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Note \/ ContentNote<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Body<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Link to Opportunity and Contact<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Action Items<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Task<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Subject + Description<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>One Task per action item, set WhoId to Contact and WhatId to Opportunity<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Next Steps<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Opportunity<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Next Step (standard field)<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Overwrite or append depending on workflow<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Highlight<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Task or Note<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Description<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Tag with &#8220;Highlight:&#8221; prefix for filtering<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Recording URL<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Task<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Description (appended)<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Include as plain URL<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Mapping Fathom Action Items to CRM Tasks<\/h2>\n<p>The cleanest approach in June 2026 for both CRMs is a one-action-item-to-one-task mapping. Batch-dumping all action items into a single Note body makes filtering and reporting almost impossible. For HubSpot, set the Task &#8220;Associated Record&#8221; to both the Contact and the Deal so follow-ups appear in both timelines.<\/p>\n<p>For Salesforce, populate both WhoId (Contact) and WhatId (Opportunity) on each Task so the item appears in both timelines. <a target=\"_blank\" rel=\"noindex nofollow\" href=\"https:\/\/help.fathom.video\/en\/articles\/448640\">If a Contact has no open Opportunities, Fathom writes the Task only to the Contact record.<\/a> Replicate this logic in your Zapier filter step to avoid orphaned tasks that never surface in pipeline reviews.<\/p>\n<h2>Common Zapier Breakage Points and Maintenance Overhead<\/h2>\n<p><a target=\"_blank\" rel=\"noindex nofollow\" href=\"https:\/\/circleback.ai\/blog\/best-ai-meeting-assistants\">Fathom lacks a native automation builder, so teams rely on Zapier to push structured meeting summaries, action items, or highlights into CRMs after calls.<\/a> That dependency introduces several recurring failure modes that compound as call volume grows.<\/p>\n<p><strong>Parsing failures.<\/strong> Zapier&#8217;s meeting-summary automations rely on custom HTML parsing and base64 decoding of event tokens across five sequential steps, meaning the workflow breaks if any single integration point fails. A Fathom template change or output format update can silently corrupt every downstream record.<\/p>\n<p><strong>Incomplete records from timing delays.<\/strong> Delays in file availability can cause incomplete CRM records and missed follow-ups.<\/p>\n<p><strong>Ongoing iteration requirement.<\/strong> Zapier itself recommends running new automations in parallel with manual processes for a week to catch edge cases, and notes that chained automations involving multiple downstream systems increase the chance of breakage.<\/p>\n<p><strong>No native AI layer.<\/strong> Zapier offers no native AI capabilities and provides only easy-to-moderate setup complexity, which creates hidden manual work as teams still need to monitor failures, mismatches, and gaps between systems.<\/p>\n<p>These four failure modes compound over time, and each Fathom update or CRM schema change creates a new maintenance ticket. Ready to skip the maintenance cycle entirely? <a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/www.coffee.ai\/pricing\"><strong>Try Coffee\u2019s native agent and eliminate Zapier maintenance<\/strong><\/a>.<\/p>\n<h2>Why Coffee\u2019s Native Agent Automation Removes These Headaches<\/h2>\n<p><a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/www.coffee.ai\/changelog\">Coffee expanded call recording options in January 2026 via Zapier integration with tools including Fathom, Gong, and Fireflies, and released improved summary templates in November 2025 that are customizable to match workflows and writable back to Coffee, HubSpot, or Salesforce.<\/a> That write-back capability is the key distinction. Coffee&#8217;s agent ingests the Fathom transcript, structures it according to your chosen sales methodology (BANT, MEDDIC, SPICED), and writes structured CRM data directly to Salesforce or HubSpot with no Zap chain, parser, or maintenance window.<\/p>\n<p>The Coffee Companion App deploys this agent as an intelligent layer on top of your existing Salesforce or HubSpot instance. It handles contact creation, activity logging, task generation, and summary templating autonomously so reps do not touch fields after each call. When Fathom&#8217;s output format changes, Coffee&#8217;s agent adapts automatically and removes the need to rebuild Zaps or re-test multi-step workflows.<\/p>\n<figure style=\"text-align: center\"><a href=\"https:\/\/www.coffee.ai\/pricing\" target=\"_blank\"><img decoding=\"async\" src=\"https:\/\/cdn.aigrowthmarketer.co\/1763678321672-5c8717cf0024.gif\" alt=\"Create instant meeting follow-up emails with the Coffee AI CRM agent\" style=\"max-height: 500px\" loading=\"lazy\"><\/a><figcaption><em>Create instant meeting follow-up emails with the Coffee AI CRM agent<\/em><\/figcaption><\/figure>\n<h2>Data Quality and Historical Accuracy: Zapier vs. Coffee<\/h2>\n<p>In 2026, CRM best practice has shifted to automatic capture from calls and documents, with AI updating deal stages, close dates, and activities within minutes of a call ending. The table below compares Fathom plus Zapier with Coffee\u2019s native agent on the dimensions that matter most to a RevOps lead.<\/p>\n<table style=\"min-width: 100px\">\n<colgroup>\n<col style=\"min-width: 25px\">\n<col style=\"min-width: 25px\">\n<col style=\"min-width: 25px\">\n<col style=\"min-width: 25px\"><\/colgroup>\n<tbody>\n<tr>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Dimension<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Fathom + Zapier<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Coffee Native Agent<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Why It Matters<\/p>\n<\/th>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Maintenance burden<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Ongoing, Zaps require monitoring for failures and mismatches<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Zero, agent adapts to source changes automatically<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>RevOps time shifts from firefighting to strategy and enablement<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Setup time<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Five or more sequential configuration steps per Zap, plus a parallel testing period<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Single authentication, agent begins syncing immediately<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Lean teams reach value faster and avoid long build cycles<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Data fidelity<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Parsing delays and format changes can produce incomplete or corrupted records<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Structured field-level write-back with historical context preserved in a data warehouse<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Accurate pipeline forecasting depends on complete, consistent history<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Cost model<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Zapier task-based pricing scales with call volume, and a separate Fathom subscription is required<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Seat-based pricing, agent labor is unlimited and included<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Costs stay predictable as meeting volume grows<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>When Zapier Makes Sense and When Coffee Fits Better<\/h2>\n<p><strong>Choose Zapier<\/strong> if your team runs fewer than 20 calls per month, your CRM schema is non-standard and requires highly custom routing logic, or you already have a dedicated RevOps engineer who maintains Zap infrastructure as part of their role.<\/p>\n<p><strong>Choose Coffee<\/strong> if your team is closing multiple deals per week, CRM data quality is a recurring agenda item in pipeline reviews, you have no dedicated automation engineer, or you want historical accuracy preserved across every deal stage change. For a 15-person SaaS team, the compounding cost of broken Zaps and incomplete records outweighs any short-term setup savings from the free Zapier tier.<\/p>\n<figure style=\"text-align: center\"><a href=\"https:\/\/www.coffee.ai\/pricing\" target=\"_blank\"><img decoding=\"async\" src=\"https:\/\/cdn.aigrowthmarketer.co\/1763678186019-5cc1a76ac78e.gif\" alt=\"Build people lists automatically with Coffee AI CRM Agent\" style=\"max-height: 500px\" loading=\"lazy\"><\/a><figcaption><em>Build people lists automatically with Coffee AI CRM Agent<\/em><\/figcaption><\/figure>\n<p>See exactly what Coffee costs for your team size. <a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/www.coffee.ai\/pricing\"><strong>View transparent seat-based pricing with no usage metering<\/strong><\/a>.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Does Coffee work with Fathom if we already use it for recording?<\/h3>\n<p>Yes. Coffee ingests transcript and summary data from Fathom and writes structured output such as tasks, notes, and deal field updates directly back to Salesforce or HubSpot. You do not need to rebuild your Fathom recording workflow. Coffee acts as the intelligence and routing layer between Fathom&#8217;s output and your CRM&#8217;s fields, replacing the Zapier chain you would otherwise maintain.<\/p>\n<figure style=\"text-align: center\"><a href=\"https:\/\/www.coffee.ai\/pricing\" target=\"_blank\"><img decoding=\"async\" src=\"https:\/\/cdn.aigrowthmarketer.co\/1763678641499-bad085f8165f.gif\" alt=\"Building a company list with Coffee AI\" style=\"max-height: 500px\" loading=\"lazy\"><\/a><figcaption><em>Building a company list with Coffee AI<\/em><\/figcaption><\/figure>\n<h3>Is Coffee secure enough for a mid-market sales team handling sensitive deal data?<\/h3>\n<p>Coffee is SOC 2 Type 2 certified and GDPR compliant. Customer data is not used to train public AI models. For mid-market RevOps teams evaluating security posture, Coffee meets the baseline requirements without the multi-year security review cycles that enterprise procurement demands.<\/p>\n<h3>How does Coffee&#8217;s pricing compare to maintaining a Zapier stack?<\/h3>\n<p>Coffee uses seat-based pricing, so you pay per human user and the agent&#8217;s labor is unlimited and included. There is no per-task metering, no separate charge for CRM write-backs, and no additional cost as call volume scales. A Zapier stack for the same workflow typically involves Zapier task costs that grow with meeting volume, plus the Fathom subscription, plus any premium Zap steps for Salesforce or HubSpot actions.<\/p>\n<h3>Can Coffee replace our existing Salesforce or HubSpot instance, or does it work alongside it?<\/h3>\n<p>Coffee operates in two modes. The Companion App deploys the Coffee agent on top of your existing Salesforce or HubSpot installation, so your system of record stays in place while Coffee handles data entry, enrichment, and post-call logging. The Standalone CRM is a separate product for teams that want Coffee as their primary system of record, typically companies with fewer than 20 employees that have outgrown spreadsheets but find legacy CRMs too maintenance-heavy.<\/p>\n<h3>What sales methodologies does Coffee support for structuring call notes?<\/h3>\n<p>Coffee&#8217;s agent can structure post-call summaries and field updates according to BANT, MEDDIC, or SPICED frameworks. This means every deal record receives consistently formatted qualification data regardless of which rep ran the call, which directly improves forecast accuracy and removes the subjectivity that makes pipeline reviews unreliable.<\/p>\n<h2>Conclusion: Moving Beyond Fragile Zapier Chains<\/h2>\n<p>Fathom Zapier CRM automation is a viable starting point, but it is not a durable solution for a growing sales team. The seven-step Zapier setup, field-mapping tables, and breakage analysis in this guide reflect the real complexity of maintaining a Zap chain between a meeting intelligence tool and a live CRM. Every format change, every Salesforce schema update, and every new edge case in your call data becomes a maintenance ticket.<\/p>\n<p>Coffee&#8217;s native agent removes that entire category of work by ingesting Fathom transcripts directly, structuring them to your sales methodology, and writing reliable CRM data back to Salesforce or HubSpot with zero pipeline interruption. <a target=\"_blank\" rel=\"noopener noreferrer nofollow\" href=\"https:\/\/www.coffee.ai\/pricing\"><strong>Replace your Zapier maintenance backlog with an agent that handles post-call updates automatically<\/strong><\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Skip the Zapier setup. Coffee&#8217;s AI agent ingests Fathom transcripts and writes structured CRM data automatically. No maintenance required.<\/p>\n","protected":false},"author":11,"featured_media":7626,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-7627","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/posts\/7627","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/comments?post=7627"}],"version-history":[{"count":0,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/posts\/7627\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/media\/7626"}],"wp:attachment":[{"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/media?parent=7627"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/categories?post=7627"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/tags?post=7627"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}