{"id":9068,"date":"2026-09-17T05:00:35","date_gmt":"2026-09-17T05:00:35","guid":{"rendered":"https:\/\/www.coffee.ai\/articles\/migrate-salesforce-workflows-to-flow"},"modified":"2026-09-17T05:00:35","modified_gmt":"2026-09-17T05:00:35","slug":"migrate-salesforce-workflows-to-flow","status":"publish","type":"post","link":"https:\/\/www.coffee.ai\/articles\/migrate-salesforce-workflows-to-flow","title":{"rendered":"How To Migrate Salesforce Workflows and Automations To Flow"},"content":{"rendered":"<p><em>Written by: Doug Camplejohn, CEO &amp; Co-Founder, Coffee<\/em><\/p>\n<h2 id=\"key-takeaways\">Key Takeaways<\/h2>\n<ul>\n<li>Salesforce ended support for Workflow Rules and Process Builder on December 31, 2025, so migration to Flow is now a cleanup project.<\/li>\n<li>A risk-tiered migration approach moves from simple field updates to complex Apex-dependent automations, which builds confidence before high-risk work.<\/li>\n<li>The Migrate to Flow tool converts roughly 70% of legacy automations cleanly but creates separate flows instead of consolidated logic and misses several automation types.<\/li>\n<li>Pending time-based actions are dropped when original rules are deactivated, so teams must inventory and trigger them manually before migration.<\/li>\n<li><a href=\"https:\/\/www.coffee.ai\/pricing\" target=\"_blank\">Maintain Salesforce Data Accuracy While Automations Are In Flux<\/a> so records stay reliable throughout migration.<\/li>\n<\/ul>\n<h2>Why Salesforce Teams Are Migrating To Flow Now<\/h2>\n<p><a href=\"https:\/\/salesforcedictionary.com\/terms\/workflow-rule\" target=\"_blank\" rel=\"noindex nofollow\">Salesforce introduced Workflow Rules in 2007 as its first declarative automation framework<\/a>. It added Process Builder in 2015. Salesforce then announced the deprecation of both in 2021 in favor of Flow. The retirement rolled out in stages. Salesforce first removed the ability to create new Workflow Rules and Process Builder processes, then ended all support on December 31, 2025.<\/p>\n<p><a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">The Migrate to Flow tool exists in Setup \u2192 Process Automation<\/a> to help admins convert legacy automation without starting from scratch. <a href=\"https:\/\/salesforcedictionary.com\/blogs\/record-triggered-flows-complete-guide-2026\" target=\"_blank\" rel=\"noindex nofollow\">It converts Workflow Rules and Process Builders cleanly in roughly 70% of cases<\/a>. The remaining 30% require manual rebuilding. The tool performs one-to-one conversion. It does not consolidate logic, audit behavior, or warn about risk patterns.<\/p>\n<p><a href=\"https:\/\/salesforcedictionary.com\/blogs\/record-triggered-flows-complete-guide-2026\" target=\"_blank\" rel=\"noindex nofollow\">As of 2026, the record-triggered Flow is the most-used automation primitive on the Salesforce platform<\/a>, and Flow is the only framework where Salesforce accepts net-new declarative builds in production orgs. Trailhead\u2019s \u201cFlow Testing and Distribution\u201d module and the official Migrate to Flow documentation cover mechanics. They do not address sequencing decisions, failure modes, or data-quality consequences while production stays live.<\/p>\n<h2>The Risk-Tiered Migration Order For Salesforce Workflows And Automations<\/h2>\n<p>This playbook sequences migrations from lowest to highest risk. Run each phase in a full sandbox before deploying to production. <a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">A full sandbox includes production data and metadata, which is essential for testing time-based actions, cross-object updates, and edge cases that only appear with real data<\/a>.<\/p>\n<ol>\n<li><strong>Phase 1 \u2014 Simple Field-Update Workflow Rules:<\/strong> Single-object, immediate-action rules with no cross-object dependencies are the safest starting point. <a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">The Migrate to Flow tool converts these into before-save record-triggered Flows correctly<\/a>. Before-save flows commit field changes before the record is written to the database. That behavior removes an entire category of DML limit errors that Process Builder often caused. Effort estimate: 15\u201330 minutes per rule.<\/li>\n<li><strong>Phase 2 \u2014 Email Alerts:<\/strong> Salesforce Email Alert objects are independent of the automation tool that triggers them, so a new record-triggered Flow can reference the same existing Email Alert without recreating its template, recipients, or sender configuration. The critical failure mode is duplicate sends. Without a change-detection condition using <code>{!$Record__Prior.StageName}<\/code>, the Flow fires on every save while the condition is true. The original Workflow Rule usually fired only on the field change. Effort estimate: 1\u20133 hours per rule.<\/li>\n<li><strong>Phase 3 \u2014 Process Builders With Single-Object Logic:<\/strong> Process Builder runs record-by-record rather than in bulk, which makes it the source of many governor limit errors on high-volume objects. Converting single-object Process Builders to record-triggered Flows removes that bottleneck. Map each Process Builder decision group\u2019s AND\/OR logic carefully. <a href=\"https:\/\/salesforcedictionary.com\/blogs\/process-builder-to-flow-migration-2026\" target=\"_blank\" rel=\"noindex nofollow\">The common mistake is building one Decision outcome with mixed conditions when the original process used OR logic<\/a>. Effort estimate: 1\u20133 hours per process.<\/li>\n<li><strong>Phase 4 \u2014 Time-Based And Scheduled Automations:<\/strong> Rules with time-dependent actions require the most pre-migration preparation. Pending actions are dropped when the original rule is deactivated, so you need a clear plan for in-flight work. Migrate during low-volume windows so fewer records sit in the queue. Manually trigger escalations that would have fired during that window. The new Flow also behaves differently at fire time. Scheduled paths in Flow re-check conditions when they run, while legacy time triggers evaluated conditions only at entry. Effort estimate: 4\u20138 hours per rule.<\/li>\n<li><strong>Phase 5 \u2014 Apex-Invoking And Integration-Dependent Automations:<\/strong> <a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Apex triggers and Workflow Rules execute in a defined order, and introducing a Flow can alter that order in ways that are not immediately obvious<\/a>. Audit every Apex trigger on objects that also have Workflow Rules. Map the execution order, then rebuild any dependencies in Apex before deactivating the rule. <a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Outbound messages have no Flow equivalent and require an Apex callout or External Service replacement, which is often a full integration rebuild<\/a>. Effort estimate: 1\u20133 weeks with a developer required.<\/li>\n<\/ol>\n<h2>What The Migrate To Flow Tool Converts And Where It Fails<\/h2>\n<p>The Migrate to Flow tool performs one-to-one conversion. An org with 15 Workflow Rules on the same object ends up with 15 separate Flows instead of one Flow with branching logic. The tool omits complexity scoring, effort estimation, and conflict detection between overlapping rules. The table below maps each legacy automation type to its Flow replacement, the level of tool support, and the main failure mode to watch.<\/p>\n<table>\n<thead>\n<tr>\n<th>Legacy Automation Type<\/th>\n<th>Flow Replacement<\/th>\n<th>Migration Tool Support<\/th>\n<th>Key Failure Mode<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Field Update<\/td>\n<td>Before-save flow<\/td>\n<td><a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Full for simple same-record updates<\/a><\/td>\n<td>None for simple same-record updates. <a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">ISCHANGED\/ISNEW must be remapped manually<\/a>.<\/td>\n<\/tr>\n<tr>\n<td>Email Alert<\/td>\n<td>Flow email action referencing existing Email Alert object<\/td>\n<td>Full (references same Email Alert object)<\/td>\n<td><a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Duplicate sends without change-detection condition<\/a><\/td>\n<\/tr>\n<tr>\n<td>Scheduled Action<\/td>\n<td>Scheduled path on record-triggered flow<\/td>\n<td><a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Partial \u2014 pending actions not migrated<\/a><\/td>\n<td><a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Pending queue dropped on deactivation<\/a><\/td>\n<\/tr>\n<tr>\n<td>Outbound Message<\/td>\n<td>Flow HTTP callout or External Service<\/td>\n<td><a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">None \u2014 silently skipped by the tool<\/a><\/td>\n<td><a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Full integration rebuild required; SOAP format rarely compatible with modern APIs<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><a href=\"https:\/\/salesforcefaqs.com\/salesforce-migrate-flow-tool\" target=\"_blank\" rel=\"noindex nofollow\">The tool also does not support Workflow Rules that use Tasks, fields on related records in criteria, record types, the &#8220;does not contain,&#8221; &#8220;includes,&#8221; or &#8220;excludes&#8221; operators on text\/picklist fields, relative date values like TODAY or NEXT WEEK, global variables, or multiple currencies<\/a>. For these, rebuild directly in Flow Builder rather than attempting a tool conversion.<\/p>\n<h2>Handling Workflow Rules With Pending Time-Based Actions<\/h2>\n<p><a href=\"https:\/\/salesforcedictionary.com\/terms\/workflow-queue\" target=\"_blank\" rel=\"noindex nofollow\">In Salesforce, the time-based workflow queue stores time-dependent actions until their scheduled time arrives<\/a>. Pending actions leave the queue in one of three ways. The scheduled time arrives and the action fires. An admin manually deletes it from Setup. Or the record that owns it is deleted.<\/p>\n<p><a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Pending time-based actions are not migrated by the Migrate to Flow tool. If the original Workflow Rule is deactivated, any records still waiting in the time-based queue will lose those pending actions<\/a>. Use this approach:<\/p>\n<ul>\n<li>Inventory what is still in the workflow queue before migration using Setup \u2192 Monitor Pending Workflow Actions.<\/li>\n<li>Migrate during a low-volume window and manually trigger escalations or follow-up actions that would have fired from the queue.<\/li>\n<li><a href=\"https:\/\/salesforcedictionary.com\/blogs\/process-builder-to-flow-migration-2026\" target=\"_blank\" rel=\"noindex nofollow\">Re-fetch the record at the start of each Scheduled Path using a Get Records element filtered by Id, then run a Decision element to confirm the record still meets the criteria before taking any action<\/a>. The record state at fire time may differ from trigger time.<\/li>\n<\/ul>\n<p><a href=\"https:\/\/salesforcedictionary.com\/blogs\/record-triggered-flows-complete-guide-2026\" target=\"_blank\" rel=\"noindex nofollow\">Scheduled paths run in a separate asynchronous transaction context with higher governor limits, 60 seconds of CPU time and 12MB of heap, and are charged against async limits rather than sync limits<\/a>. They can also be silently canceled if the flow\u2019s entry conditions no longer hold before the scheduled fire time. That behavior often surprises teams when a scheduled job vanishes without explanation.<\/p>\n<h2>Subflows Vs. Actions: Consolidation Strategy For Record-Triggered Flows<\/h2>\n<p><a href=\"https:\/\/salesforcedictionary.com\/blogs\/record-triggered-flows-complete-guide-2026\" target=\"_blank\" rel=\"noindex nofollow\">Salesforce evaluates multiple record-triggered flows on the same object in alphabetical order, and that order can affect outcomes<\/a>. The long-standing best practice favored one flow per object organized internally with subflows. However, <a href=\"https:\/\/dianapps.com\/blog\/the-ultimate-guide-to-salesforce-flow\" target=\"_blank\" rel=\"noindex nofollow\">Salesforce\u2019s Flow Trigger Explorer lets admins see every record-triggered flow on an object in execution order and reorder them<\/a>. That visibility has shifted many teams toward several focused flows per object with a deliberate execution order instead of one monolith.<\/p>\n<p>Several constraints govern where subflows can be used:<\/p>\n<ul>\n<li><a href=\"https:\/\/certifysf.com\/subflows-in-salesforce\" target=\"_blank\" rel=\"noindex nofollow\">Before-save (Fast Field Updates) record-triggered flows cannot contain a Subflow element<\/a>. They support only Assignment, Decision, Get Records, and Loop elements. After-save flows are the natural place for reusable orchestration that needs subflows.<\/li>\n<li><a href=\"https:\/\/certifysf.com\/subflows-in-salesforce\" target=\"_blank\" rel=\"noindex nofollow\">A Subflow element can reference only autolaunched flows and screen flows<\/a>. It cannot launch record-triggered, schedule-triggered, or platform event-triggered flows.<\/li>\n<li><a href=\"https:\/\/certifysf.com\/subflows-in-salesforce\" target=\"_blank\" rel=\"noindex nofollow\">Subflows run in the parent flow\u2019s transaction and share the same governor limits<\/a>. SOQL, DML, and CPU counters are not reset by entering a subflow.<\/li>\n<\/ul>\n<p><a href=\"https:\/\/salesforcedictionary.com\/blogs\/record-triggered-flows-complete-guide-2026\" target=\"_blank\" rel=\"noindex nofollow\">Avoid recursion across flows, where Flow A updates a record that fires Flow B, which updates the same record and fires Flow A again<\/a>. Use a single flow with internal branches when the logic is related. For recursive Workflow Rule chains, <a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">the safe Flow equivalent is a single record-triggered flow with decision elements and a WF_Processed__c checkbox guard that skips the flow if already true<\/a>.<\/p>\n<h2>Testing And Verification Before Deactivating Legacy Automation<\/h2>\n<p><a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Keep the original Workflow Rule active until the replacement Flow has run correctly in production for at least two weeks<\/a>. Use the following checklist to verify each migration before cutover.<\/p>\n<ul>\n<li><strong>Bulk Load Test:<\/strong> <a href=\"https:\/\/salesforcedictionary.com\/blogs\/process-builder-to-flow-migration-2026\" target=\"_blank\" rel=\"noindex nofollow\">Load 200 records to check governor limits under volume<\/a>. A flow that works on one record can fail on two hundred.<\/li>\n<li><strong>Single-Record Debug Trace:<\/strong> Use Flow Builder\u2019s Debug pane to run both the main path and the skip path. Verify variable values at each step.<\/li>\n<li><strong>Side-By-Side Comparison Run:<\/strong> <a href=\"https:\/\/salesforcedictionary.com\/blogs\/process-builder-to-flow-migration-2026\" target=\"_blank\" rel=\"noindex nofollow\">Trigger the old process and the new flow against equivalent records and compare the resulting field values<\/a>.<\/li>\n<li><strong>Negative Test Cases:<\/strong> <a href=\"https:\/\/martechnotes.com\/how-to-test-your-salesforce-flow\" target=\"_blank\" rel=\"noindex nofollow\">Include at least one negative test case per decision element<\/a>, such as \u201cCustomer Type is blank\u201d or \u201cAmount is 0,\u201d because those record states appear frequently in production.<\/li>\n<li><strong>Post-Deploy Monitoring:<\/strong> <a href=\"https:\/\/salesforcefaqs.com\/salesforce-migrate-flow-tool\" target=\"_blank\" rel=\"noindex nofollow\">Monitor migrated Flows for errors by checking Setup \u2192 Flows, Flow Error Emails, and Paused and Failed Flow Interviews<\/a> for the first several days after production activation.<\/li>\n<\/ul>\n<p>After verifying a migrated Flow, deactivate the original Workflow Rule rather than delete it. <a href=\"https:\/\/salesforcedictionary.com\/blogs\/record-triggered-flows-complete-guide-2026\" target=\"_blank\" rel=\"noindex nofollow\">For the roughly 30% of automations that Migrate to Flow cannot convert cleanly, admins should rebuild manually and then delete the originals rather than leaving them disabled-but-present, because a disabled automation in Setup is one careless click away from becoming an enabled regression<\/a>.<\/p>\n<p> <a href=\"https:\/\/www.coffee.ai\/pricing\" target=\"_blank\"><strong>Keep Your Salesforce Data Clean During Migration<\/strong><\/a><\/p>\n<h2>Post-Migration Data Quality And Reporting Impact<\/h2>\n<p><a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Reports themselves do not break when migrating from Workflow Rules to Flow because they read field values, not the automation that sets them<\/a>. If a migrated Flow has a bug that causes field updates to fire at the wrong time or not at all, report data will drift. Outbound message replacements require full integration rebuilds. Any downstream system that consumed those SOAP payloads needs to be re-pointed to the new callout or External Service before the legacy rule is deactivated.<\/p>\n<p>Migration also exposes a deeper data-entry problem. Legacy CRMs like Salesforce rely on busy humans to enter data, and that dependency continues when Workflow Rules become Flows. 71% of sales reps say they spend too much time on data entry, leaving only 35% of their time for selling. When automations are in flux during migration, the manual data entry problem compounds. Records that automations were keeping current now depend entirely on human input.<\/p>\n<p>Coffee\u2019s Companion App for Salesforce deploys as an intelligent agent layer on top of an existing Salesforce installation. The Coffee Agent handles the data-in process, capturing tasks, logging interactions, enriching contacts, and syncing activity from emails and calls. Salesforce records stay accurate without manual effort. Coffee does not migrate Workflow Rules or Process Builder. It addresses the data-quality layer that migration work leaves untouched. Coffee is SOC 2 Type 2 and GDPR compliant, and data is not used to train public models.<\/p>\n<h2>How Flow Changes Salesforce\u2019s Automation Operating Model<\/h2>\n<p><a href=\"https:\/\/dianapps.com\/blog\/the-ultimate-guide-to-salesforce-flow\" target=\"_blank\" rel=\"noindex nofollow\">Process Builder is retired. Existing processes continue to execute, but Salesforce will not fix bugs in them, will not support them when they break after a platform update, and has made clear that the long-term future is Flow<\/a>. Orgs still running Process Builder are operating on borrowed time.<\/p>\n<p>The operating model shift from Workflow Rules and Process Builder to Flow changed more than the tool name. <a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Workflow Rules evaluated multiple rules on the same object in alphabetical order by name<\/a>. <a href=\"https:\/\/luxeracloud.com\/blog\/salesforce-workflow-rule-to-flow-migration\" target=\"_blank\" rel=\"noindex nofollow\">Multiple record-triggered Flows on the same object run in an order controlled via trigger ordering<\/a>, which gives admins explicit control that Workflow Rules never provided. <a href=\"https:\/\/salesforcedictionary.com\/blogs\/process-builder-to-flow-migration-2026\" target=\"_blank\" rel=\"noindex nofollow\">Before-save flows run earlier in the order of execution than Workflow Rules did<\/a>. That timing means naively converting both a Workflow Rule that set a field and a Process Builder that read that field on the same record edit can flip the read and write order.<\/p>\n<h2>Conclusion: How To Use This Playbook<\/h2>\n<p>Migrating Salesforce workflows and automations to Flow forces teams to surface years of automation debt, resolve sequencing conflicts, handle in-flight scheduled actions, and rebuild integrations that outbound messages were quietly powering. Admins who migrate blindly with the Migrate to Flow tool, without a risk-tiered plan, inherit the same operational mess in a new framework plus new Flow-specific failure modes around recursion, order of execution, and bulk processing.<\/p>\n<p>The playbook above sequences migrations from lowest to highest risk, calls out realistic failure modes for each phase, and provides a testing protocol that catches regressions before they reach production. Migration work still leaves one core dependency in place. Salesforce records stay accurate only when someone or something keeps putting good data in. Coffee\u2019s Companion App for Salesforce deploys as an intelligent agent on top of your existing installation, handling the data-in process automatically so your team spends time selling instead of updating records.<\/p>\n<p> <a href=\"https:\/\/www.coffee.ai\/pricing\" target=\"_blank\"><strong>Give Your Salesforce Org A Reliable Data-Quality Layer<\/strong><\/a><\/p>\n<section data-read-next=\"true\">\n<h2>Read Next<\/h2>\n<ul>\n<li><a href=\"https:\/\/coffee.ai\/articles\/salesforce-migration-automation-2026\" target=\"_blank\">Salesforce Migration Automation: Tools &amp; Best Practices<\/a><\/li>\n<li><a href=\"https:\/\/coffee.ai\/articles\/best-ways-automate-salesforce-processes\" target=\"_blank\">Top 10 Ways to Automate Salesforce Processes in 2026<\/a><\/li>\n<li><a href=\"https:\/\/coffee.ai\/articles\/salesforce-migration-tools-2026\" target=\"_blank\">Salesforce Migration Tools: Find the Lowest-Risk Option<\/a><\/li>\n<li><a href=\"https:\/\/coffee.ai\/articles\/how-to-migrate-to-salesforce\" target=\"_blank\">How to Migrate to Salesforce: A Decision-First Guide<\/a><\/li>\n<li><a href=\"https:\/\/coffee.ai\/articles\/salesforce-data-migration-best-practices\" target=\"_blank\">Salesforce Data Migration Best Practices: An 8-Step Playbook<\/a><\/li>\n<\/ul>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>Learn how to migrate Salesforce Workflows to Flow with a risk-tiered playbook. Coffee helps you automate smarter. Start your migration today.<\/p>\n","protected":false},"author":11,"featured_media":9067,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-9068","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\/9068","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"}],"replies":[{"embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/comments?post=9068"}],"version-history":[{"count":0,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/posts\/9068\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/media\/9067"}],"wp:attachment":[{"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/media?parent=9068"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/categories?post=9068"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/tags?post=9068"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}