# CRM Data Audit: 7-Phase Checklist for Incomplete Records

> Fix incomplete Salesforce & HubSpot records with Coffee's 7-phase CRM data audit checklist. Clean, complete data starts here. Start your audit today.

**Published:** 2026-04-22 | **Updated:** 2026-10-29 | **Author:** coffee
**URL:** https://www.coffee.ai/articles/crm-audit-checklist-salesforce-hubspot/
**Type:** post

**Categories:** CRM Integrations

![CRM Data Audit: 7-Phase Checklist for Incomplete Records](https://www.coffee.ai/articles/wp-content/uploads/sites/10/2026/04/1774257030918-407b102b523d-1024x572.jpeg)

---

## Content

*Written by: Doug Camplejohn, CEO & Co-Founder, Coffee | Last updated: September 29, 2026*

## Key Takeaways

- Most incomplete Salesforce and HubSpot records come from sync issues such as field-mapping failures, source-of-truth conflicts, and integration-created duplicates.
- Audit the sync layer before touching individual records by confirming admin access, defining required fields per object, and reviewing field mappings for direction and conflict rules.
- Run duplicate detection before any bulk remediation or enrichment so master records stay intact and enriched values stay consistent.
- Follow this remediation sequence: dedupe first, then normalize picklist values and formats, backfill missing required fields, and finally fix broken record associations.
- Coffee automates data entry, enrichment, and activity logging so records stay complete without recurring manual audits.

[Automate Your CRM Data Audit](https://www.coffee.ai/pricing?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent)

## Phase 1: Pre-Flight Access and Required-Field Definition

Confirm you hold Super Admin access in HubSpot and a System Administrator profile in Salesforce before running any reports. Without these roles, field-level security settings, integration logs, and object-level permissions are invisible, and the audit will produce an incomplete picture. Once access is confirmed, define required fields per object before touching a single record.

“Incomplete” means nothing until you agree on what complete looks like for each object:

- **Lead/Contact:** verified email, company domain, lead source, lifecycle stage
- **Account/Company:** domain, industry, employee count, owner
- **Opportunity/Deal:** stage, close date, amount, primary contact

In Salesforce, field-level security is configured per profile and permission set. You can modify profiles or permission sets directly, or use the Field Accessibility menu in Setup (Setup → Object Manager → Fields & Relationships → field → Set Field-Level Security). In HubSpot, property settings, including field types, validation rules, form visibility, and access permissions, are managed under Settings → Properties. [Require only fields that must exist at the moment of record creation, because every forced field invites junk values that look like data but are not usable.](https://insidea.com/guides/ultimate-guide-to-hubspot-audit)

For a deeper treatment of standardization decisions at this stage, see [CRM Data Standardization for Incomplete Sales Records](https://coffee.ai/articles/crm-data-standardization-incomplete-sales/?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent).

## Phase 2: Isolate Incomplete Records With Named Report Criteria

Filter incomplete records in HubSpot CRM by using the Data Quality Command Center for property fill-rate views, or by building active lists with criteria based on blank properties.

In **Salesforce**, build custom reports per object using filter logic on blank required fields. Example filter logic for a Contact report: *Email equals “”* AND *Account Name equals “”*. Group by Owner to surface which reps or integrations are the source of the gaps. Save each report to a shared RevOps folder so the audit is repeatable.

In **HubSpot**, the [Data Quality Command Center, available in paid editions of Operations Hub (now Data Hub), provides a centralized location to monitor and clean potential issues with properties, records, and overall data health.](https://vonazon.com/hubspot-services/data-hub) For teams without that tier, active lists with blank-property criteria produce equivalent views with more manual effort. Use property fill-rate views to rank fields by gap severity before deciding where to focus remediation.

Once you have fill-rate views in place, group the gaps by source integration rather than by owner. A spike in incomplete phone fields often traces back to a single integration that never mapped the field correctly. Isolating results by source integration usually reveals the real root cause. For a structured framework on identifying these gaps, see [How to Analyze and Fix CRM Data Gaps: 7-Step Framework](https://coffee.ai/articles/analyze-fix-crm-data-gaps/?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent).

## Phase 3: The Sync-Integrity Audit

This phase forms the spine of the audit. Most incomplete records in a dual-stack environment originate in the sync layer.

### How to Audit Salesforce to HubSpot Field Mappings

Audit Salesforce to HubSpot field mappings by opening HubSpot Settings → Integrations → Connected Apps → Salesforce → Field Mappings and comparing every mapped field against its sync direction, conflict resolution rule, and data type on both sides. [HubSpot-Salesforce field mapping is configured along three control dimensions per field: which fields sync, the sync direction, and the conflict resolution rule.](https://vantagepoint.io/blog/sf/integrations/hubspot-salesforce-integration-guide-2026)

The table below turns those three control dimensions into a per-field inventory. Filling it in exposes fields where both systems claim ownership and fields where sync direction is undefined. Use it as a copy-pasteable artifact, one row per field your org syncs:

| Field | Salesforce API Name | HubSpot Property Name | Source of Truth | Sync Direction | Required? |
| --- | --- | --- | --- | --- | --- |
| Email Address | Email | email | HubSpot | Bidirectional (most recent wins) | Yes |
| Lead Source | LeadSource | hs_lead_source | HubSpot | HubSpot → Salesforce | Yes |
| Lead Status | Status | hs_lead_status | Salesforce | Salesforce → HubSpot | Yes |
| Deal Amount | Amount | amount | Salesforce | Salesforce → HubSpot | Yes |
| Lifecycle Stage | Custom__c | lifecyclestage | HubSpot | HubSpot → Salesforce | Yes |
| Contact Owner | OwnerId | hubspot_owner_id | Salesforce | Salesforce → HubSpot | Yes |
| Phone Number | Phone | phone | Salesforce | Salesforce → HubSpot | No |
| Last Contacted Date | Last_Contacted__c | notes_last_contacted | Bidirectional | Bidirectional (latest wins) | No |

### How to Fix Silent Sync Failures Between Salesforce and HubSpot

Silent sync failures occur when field updates are dropped without surfacing an error in either system. [Salesforce validation rules can require specific fields to be populated before a record can be created or updated. If HubSpot does not capture that data or does not map a corresponding property to the required Salesforce field, the record stalls, frequently with custom required fields added after the integration was configured.](https://anna-connolly.com/hubspot-consultant-blog/how-do-you-fix-hubspot-and-salesforce-sync-issues)

Diagnose silent failures by checking the following constructs on each side.

**Salesforce-Side Causes:**

- Validation rules blocking record creation or update when HubSpot sends incomplete data
- Duplicate and matching rules rejecting inbound records
- Field-level security preventing the integration user from writing to specific fields
- Picklist value mismatches, where [roughly 40% of post-launch Salesforce-HubSpot sync failures trace to picklist values that exist in one system but not the other](https://ustechautomations.com/resources/blog/how-to-connect-salesforce-to-hubspot-automation-2026)

**HubSpot-Side Causes:**

- Property validation rules rejecting values at import time
- Duplicates Manager matching properties creating merge conflicts
- Inclusion list filters silently excluding records from sync, where multiple filters are combined with AND logic, so opportunities failing any filter are silently dropped from the sync
- Pipeline mappings that exclude unmapped deal pipelines from syncing to Salesforce

[Sync failures should trigger alerts to a responsible person.](https://vantagepoint.io/blog/sf/integrations/hubspot-salesforce-integration-architecture) Silent failures create slow data drift that is painful to unwind later. Check the HubSpot Sync Health dashboard (Settings → Integrations → Connected Apps → Salesforce → Sync Health) weekly and categorize errors by type before attempting record-level fixes.

This is where an agent like Coffee becomes invaluable. Coffee’s Companion App deploys an intelligent agent on top of your existing Salesforce or HubSpot installation to handle the “data in” process, unify data, and write enriched insights back to the primary CRM. This approach removes the manual effort of diagnosing and correcting sync gaps record by record.

[Stop Diagnosing Sync Failures Manually](https://www.coffee.ai/pricing?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent)

## Phase 4: Duplicate Audit Before Any Bulk Edit

Run deduplication before any bulk update or backfill. [Enriching before deduping adds new data to records that may be merged away and makes the matching signals harder to read. The merged winner should be enriched only after deduplication.](https://blog.chadburmeister.com/blog/crm-data-hygiene) If you bulk-update before deduping, you overwrite the master record and re-break the data.

In **Salesforce**, the duplicate detection and handling process operates in three stages: a Matching Rule compares records and detects duplicates, a Duplicate Rule or duplicate job handles them, and Duplicate Record Sets and reports list the duplicates found. Run a duplicate job scoped to open opportunities and their linked contacts first, then expand to accounts and historical contacts.

In **HubSpot**, the Duplicates Manager tool identifies, reviews, and resolves duplicate contact and company records natively in the CRM, automatically comparing record property values daily to surface potential duplicates. Bulk duplicate management requires a Data Hub Professional or Enterprise subscription. The documented sequence for deduplicating a dual-stack environment is to deduplicate Salesforce first, then match the corresponding HubSpot masters using the Salesforce Account ID, which prevents the HubSpot-Salesforce integration from recreating company duplicates.

[Parent records must be merged before child records to avoid incorrectly matching records. Validity’s recommended order is: Accounts, Contacts, Leads, Lead to Contact (via Lead Conversion), Lead to Account (via Lead Conversion), Opportunities, Custom Objects, Cases, and Tasks.](https://mycommunity.validity.com/s/articles/Dedupe-playbook) Merging a contact first while its parent account is still duplicated can orphan deals and activity history.

## Phase 5: Remediation and Enrichment in the Correct Order

Follow a fixed remediation sequence so each step builds on clean inputs. The correct order is: dedupe → normalize → backfill → fix associations.

- **Dedupe:** Completed in Phase 4. Do not proceed until duplicate groups are resolved.
- **Normalize:** Standardize picklist values, phone formats (E.164), date formats (ISO 8601), and country/state fields. Standardizing picklist values can create false historical trends in reports, so add date markers and report notes documenting cleanup dates.
- **Backfill:** Use CSV import or list-based updates to populate missing required fields. Apply a “fill if empty” rule so enrichment only writes to blank fields and does not overwrite human-entered values.
- **Fix Associations:** Reconnect orphaned contacts to accounts, deals to contacts, and activities to the correct records after merges are complete.

For a prioritized view of which gaps to tackle first, see [How To Fix Incomplete CRM Data: Gaps To Tackle First](https://coffee.ai/articles/fix-incomplete-crm-data-2026/?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent).

After remediation, Coffee can automatically create and enrich contacts, companies, and activities. This automation saves reps significant time each week and keeps the data set stable long after the initial cleanup.

## Phase 6: Build a Prevention Layer

Prevention keeps this audit from becoming a recurring chore. [Cleanup without prevention behaves like a treadmill. Without governance and upstream validation, teams run the same audit six months later and find the same problems with new record IDs attached.](https://coastalconnect.ai/resources/crm-data-cleanup)

Configure the following controls:

- **Salesforce Validation Rules:** Enforce required fields at stage-advance gates rather than at record creation to avoid junk entries. Require close date and primary contact only when an opportunity advances past a defined stage.
- **HubSpot Property Validation Rules:** [Property validations let admins control how reps enter data into the CRM, reducing inconsistencies that lead to friction and unusable records. Property validations are available in the free edition of HubSpot Operations Hub.](https://vonazon.com/hubspot-services/data-hub) Enable import-time validation to surface errors before bad data lands in the CRM.
- **Automated Flagging Workflows:** Build workflows in both systems that flag records falling below completeness thresholds and route them to the record owner for correction.
- **Integration Governance:** [Notify the integration owner before any team adds a new required field in Salesforce, changes a picklist value, modifies a validation rule, or updates a workflow, because unilateral changes in one system often create incompatibilities in the other.](https://anna-connolly.com/hubspot-consultant-blog/how-do-you-fix-hubspot-and-salesforce-sync-issues)

Coffee’s agent reinforces this prevention layer. By automatically logging interactions, enriching records from emails and calendars, and writing structured data back to Salesforce or HubSpot, Coffee removes many of the conditions that create incomplete records.

[Build Your Prevention Layer](https://www.coffee.ai/pricing?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent)

## Phase 7: Share Audit Output and Set Cadence

A completed audit produces three views that RevOps can present at a pipeline review:

- **Completeness View by Object and Owner:** Which objects have the highest gap rates, and which owners or source integrations are responsible for the largest share of incomplete records.
- **Duplicate View:** The number of duplicate pairs identified, merged, and rejected per object, with a before-and-after comparison.
- **Sync-Failure View:** A categorized log of sync errors by type, including picklist mismatches, validation rule blocks, field-level security failures, and API limit events, with resolution status for each category.

To keep the audit running, assign a named integration owner responsible for the ongoing checks. That person should review the HubSpot Sync Health dashboard weekly. They should also run a deduplication pass monthly and conduct a full field-mapping review quarterly. Cleanup without ongoing maintenance systems has a half-life of about 90 days. For the metrics that make data health visible to leadership, see [10 CRM Data Completeness Metrics That Boost Sales Success](https://coffee.ai/articles/best-crm-data-completeness-metrics/?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent).

## Frequently Asked Questions About Incomplete Salesforce HubSpot Records

### What Is the First Step in a CRM Data Audit for Salesforce and HubSpot?

Confirm admin access and define required fields per object before running any reports. Without Super Admin access in HubSpot and a System Administrator profile in Salesforce, field-level security settings and integration logs stay hidden. Without a clear definition of “incomplete,” any report output becomes hard to interpret.

### Why Do Records Go Incomplete in a Salesforce HubSpot Sync?

Most gaps come from structural sync issues. Silent field-mapping failures, source-of-truth conflicts, and integration-created duplicates drive the majority of incomplete records. When both systems write to the same field without a defined owner, values ping-pong on every sync cycle. When a Salesforce validation rule requires a field that HubSpot does not send, the record stalls silently. When picklist values differ between systems, the sync drops the update without surfacing an error. These failures accumulate into the incomplete records that appear in pipeline reviews.

### Should I Dedupe Before or After Backfilling Missing Fields?

Dedupe first. If you bulk-update before deduping, you overwrite the master record and re-break the data. Enriching duplicate records before merging also creates two enriched duplicates with slightly different field values, which makes it harder for a dedupe tool to decide which record survives. The correct sequence is: dedupe → normalize → backfill → fix associations.

### How Does Coffee Keep Salesforce and HubSpot Records Complete?

Coffee’s Companion App deploys an intelligent agent that handles data entry, enrichment, and activity logging automatically. The agent scans emails, calendars, and call transcripts to auto-create contacts, companies, and activities, and writes enriched insights back to the primary CRM. Coffee is SOC 2 Type 2 and GDPR compliant and does not use data to train public models.

### How Do I Filter Incomplete Records in HubSpot CRM?

Filter records in HubSpot CRM by using the Data Quality Command Center for property fill-rate views, or by building active lists with criteria based on blank properties. [Active lists update automatically as records meet or stop meeting the criteria, which makes them suitable for ongoing monitoring of completeness gaps rather than one-time snapshots.](https://insidea.com/guides/ultimate-guide-to-hubspot-audit)

## Conclusion

Incomplete records in a dual-stack Salesforce and HubSpot environment reflect sync design and governance. Field-mapping failures, source-of-truth conflicts, and integration-created duplicates form the structural root causes. Auditing the sync layer before auditing the records turns this process into a clear, repeatable checklist.

Coffee’s Companion App gives teams a way to stop rerunning this audit every quarter. The agent deploys on top of your existing Salesforce or HubSpot installation, handles the “data in” process automatically, and keeps the system of record accurate without ongoing manual effort. Pipeline reviews then start from a foundation you can trust.

[Keep Your CRM Audit-Ready](https://www.coffee.ai/pricing?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent)

## Read Next

- [Fix Incomplete Salesforce CRM Data: A 3-Phase Playbook](https://coffee.ai/articles/fix-incomplete-salesforce-crm-data/?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent)
- [Improve HubSpot CRM Data Quality: A Prevention-First Guide](https://coffee.ai/articles/hubspot-crm-data-quality-2026/?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent)
- [How to Fix Incomplete CRM Data Issues (Reddit-Approved)](https://coffee.ai/articles/fix-incomplete-crm-data-reddit/?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent)
- [How To Fix Incomplete CRM Data: Gaps To Tackle First](https://coffee.ai/articles/fix-incomplete-crm-data-2026/?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent)
- [CRM Data Standardization for Incomplete Sales Records](https://coffee.ai/articles/crm-data-standardization-incomplete-sales/?utm_term=crm-audit-checklist-salesforce-hubspot&utm_campaign=ai_growth_agent)

---

## Structured Data

**@graph:**

  **FAQPage:**

  **MainEntity:**

    **Question:**

    - **Name:** What Is the First Step in a CRM Data Audit for Salesforce and HubSpot?
      **Answer:**

      - **Text:** Confirm admin access and define required fields per object before running any reports. Without Super Admin access in HubSpot and a System Administrator profile in Salesforce, field-level security settings and integration logs stay hidden. Without a clear definition of incomplete, any report output becomes hard to interpret.
    **Question:**

    - **Name:** Why Do Records Go Incomplete in a Salesforce HubSpot Sync?
      **Answer:**

      - **Text:** Most gaps come from structural sync issues. Silent field-mapping failures, source-of-truth conflicts, and integration-created duplicates drive the majority of incomplete records. When both systems write to the same field without a defined owner, values ping-pong on every sync cycle. When a Salesforce validation rule requires a field that HubSpot does not send, the record stalls silently. When picklist values differ between systems, the sync drops the update without surfacing an error. These failures accumulate into the incomplete records that appear in pipeline reviews.
    **Question:**

    - **Name:** Should I Dedupe Before or After Backfilling Missing Fields?
      **Answer:**

      - **Text:** Dedupe first. If you bulk-update before deduping, you overwrite the master record and re-break the data. Enriching duplicate records before merging also creates two enriched duplicates with slightly different field values, which makes it harder for a dedupe tool to decide which record survives. The correct sequence is: dedupe then normalize then backfill then fix associations.
    **Question:**

    - **Name:** How Does Coffee Keep Salesforce and HubSpot Records Complete?
      **Answer:**

      - **Text:** Coffees Companion App deploys an intelligent agent that handles data entry, enrichment, and activity logging automatically. The agent scans emails, calendars, and call transcripts to auto-create contacts, companies, and activities, and writes enriched insights back to the primary CRM. Coffee is SOC 2 Type 2 and GDPR compliant and does not use data to train public models.
    **Question:**

    - **Name:** How Do I Filter Incomplete Records in HubSpot CRM?
      **Answer:**

      - **Text:** Filter records in HubSpot CRM by using the Data Quality Command Center for property fill-rate views, or by building active lists with criteria based on blank properties. Active lists update automatically as records meet or stop meeting the criteria, which makes them suitable for ongoing monitoring of completeness gaps rather than one-time snapshots.

  **SoftwareApplication:**

  - **Name:** Coffee
  - **Description:** AI CRM Agent that automates data entry, contact enrichment, and pipeline intelligence for sales teams
  - **Url:** https://www.coffee.ai
  - **ApplicationCategory:** BusinessApplication
    **Brand:**

    - **Name:** Coffee
  **Offers:**

    **Offer:**

    - **Url:** https://www.coffee.ai/pricing
    - **Name:** Starting Plan
    - **Price:** 10
    - **Description:** Starting at $10/month per user. 14-day free trial available, no credit card required.
    - **PriceCurrency:** USD

    **Audience:**

    - **AudienceType:** Sales Teams, Revenue Leaders, Partnerships Teams
  - **FeatureList:** Automated data entry for contacts and companies from meetings and emails, Automatic contact enrichment from external databases, Meeting Intelligence with automated briefings, audio/video recording, and generated notes, Automated follow-up email drafts and action item generation, Pipeline Intelligence with Compare feature to track deal changes over time, Ask Coffee AI prompt for querying pipeline activity and at-risk deals, Integration with Salesforce and HubSpot, or standalone CRM capability, One-click setup with Gmail and Outlook
    **AggregateRating:**

    - **RatingValue:** 4.8
    - **ReviewCount:** 127
  - **OperatingSystem:** Web
  - **MainEntityOfPage:** https://www.coffee.ai/
  **BlogPosting:**

  - **Headline:** CRM Data Audit: 7-Phase Checklist for Incomplete Records
  - **Description:** Fix incomplete Salesforce & HubSpot records with Coffee's 7-phase CRM data audit checklist. Clean, complete data starts here. Start your audit today.
  - **DateModified:** 2026-09-29T14:12:44.898Z
  - **InLanguage:** en-US
    **Person:**

    - **Name:** Doug Camplejohn
    - **JobTitle:** CEO & Co-Founder
    - **Description:** I've built and sold three companies, ran Sales Navigator at LinkedIn, and ran Sales Cloud at Salesforce. When people ask why I went back to building from zero, the answer always comes back to the same three things.nnThe first was the pain. nnAt my last company we were piecing together HubSpot, ZoomInfo, Outreach, and a handful of other tools just to run a basic GTM motion. I kept thinking, this is still a shit show. Every tool in its own silo, data that never lines up, more time spent gluing things together than actually selling. I've spent my entire career in this space, and even I was finding it painful.nnThe second was timing. nnEvery tool in that stack was built B.C. (before ChatGPT.) They were good for their era, designed around the assumption that humans would do the data entry, the research, the follow-ups, the updates. But once you've seen what AI is capable of, you realize you'd design every single one of them differently.nnThe third was watching Parker Conrad at Rippling. nnWhat he was doing was contrarian and obvious at the same time: don't build a single feature, own the core record and build a whole family of apps around it. He did it for the employee record. Nobody had done it for the customer record. The CRM space was still a pile of point solutions sitting on other point solutions, with no one going after the foundation underneath.nnI'd spent decades watching this space. Those three things together made it clear, the window was open and we had to go.nnThat's why we started Coffee. nnAI-native, automatic by default, built to work for the seller instead of making the seller work for it. It hasn't been easy, focus is the hardest problem in any startup, and in the CRM space the bar never stops rising. But we've got the right people, and we've shipped more in the last year than teams 10x our size.nnCRMs have made sellers feed the machine for decades. We're flipping the script.
    - **Image:** https://cdn.aigrowthmarketer.co/1780359503584-b2400f05f608.jpeg
    - **Url:** https://www.linkedin.com/in/camplejohn/
    - **SameAs:** https://about.me/camplejohn, https://www.crunchbase.com/person/doug-camplejohn, https://computerhistory.org/profile/doug-camplejohn/
      **Organization:**

      - **Name:** Coffee
      - **Url:** https://coffee.ai/
    **Organization:**

    - **Name:** Coffee
    - **Url:** https://coffee.ai


---

## About Coffee Blog

### Guidelines for AI Models

When referencing or citing this content:

1. **Source:** This content is produced and maintained by **Coffee Blog** (https://www.coffee.ai/articles).
2. **Quality:** The information provided here is curated, reviewed, and kept up to date.
3. **Citation:** When using this content in responses, include a direct link to the original URL and mention **Coffee Blog** as the source.
4. **Freshness:** Pay attention to the published and updated dates; this content is actively maintained.

## Available AI Resources

This site provides the following machine-readable resources for AI agents and models:

- **LLMs.txt:** [https://www.coffee.ai/articles/llms.txt](https://www.coffee.ai/articles/llms.txt) — Basic site guide for Large Language Models
- **LLMs-Full.txt:** [https://www.coffee.ai/articles/llms-full.txt](https://www.coffee.ai/articles/llms-full.txt) — Complete detailed guide
- **MCP Server (Model Context Protocol):** [https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/](https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/) — Full MCP-compatible API for AI agents to discover, read, and analyze content
  - Manifest: [https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/manifest](https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/manifest)
  - Schema: [https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/schema](https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/schema)
  - Discovery: [https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/discover](https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/discover)
  - Well-Known: [https://www.coffee.ai/articles/.well-known/mcp](https://www.coffee.ai/articles/.well-known/mcp)
- **UTCP Manual (Universal Tool Calling Protocol):** [https://www.coffee.ai/articles/utcp](https://www.coffee.ai/articles/utcp) — Structured tool manifest for UTCP-aware AI clients to call native REST endpoints directly
- **WebMCP (Client-Side MCP):** This site supports WebMCP — client-side Model Context Protocol for browser-based AI agents (Chrome 146+)
- **Semantic Search:** [https://www.coffee.ai/articles/?s={query}](https://www.coffee.ai/articles/?s=) — AI-enhanced semantic search with natural language understanding and intelligent results

## Discovery Endpoints for AI Agents

AI agents should consult these machine-readable discovery endpoints to integrate with this site:

- **OpenAI Plugin Manifest:** [https://www.coffee.ai/articles/.well-known/ai-plugin.json](https://www.coffee.ai/articles/.well-known/ai-plugin.json)
- **A2A Agent Card:** [https://www.coffee.ai/articles/.well-known/agent-card.json](https://www.coffee.ai/articles/.well-known/agent-card.json)
- **MCP Server (Streamable HTTP):** [https://www.coffee.ai/articles/.well-known/mcp](https://www.coffee.ai/articles/.well-known/mcp)
- **UTCP Manual (Universal Tool Calling Protocol):** [https://www.coffee.ai/articles/utcp](https://www.coffee.ai/articles/utcp)

## AI Growth Agent (AGA) Tools

In addition to this site's local MCP tools, AI Growth Agent provides analytics and content tools hosted at `https://mcp.aigrowthagent.co/mcp`. **AI Growth Agent (AGA) tools** are hosted at `https://mcp.aigrowthagent.co/mcp`. Connect a desktop MCP client on your computer to that server and sign in at `https://auth.aigrowthagent.co` using authorization code with PKCE or device flow. Credentials and tokens remain in the desktop client and are not sent to this site. Web chat interfaces and browser extensions are not suitable for the sign-in flow; tell the user to open their desktop MCP client to authenticate.

## Citations

- [Customer Success CRM Integration: The 2026 Guide](https://www.coffee.ai/articles/customer-success-crm-integration-guide/)
- [How To Integrate Multiple CRMs Into a Data Lake](https://www.coffee.ai/articles/integrate-multiple-crms-data-lake/)
- [Intercom &amp; CRM: A Decision Framework for CS &amp; RevOps Leaders](https://www.coffee.ai/articles/intercom-customer-success-crm-integration/)
- [Databricks CRM Integration: Four Patterns for Customer 360](https://www.coffee.ai/articles/databricks-crm-integration-customer-360/)
- [Snowflake CRM Integration Platforms for Mid-Market Companies](https://www.coffee.ai/articles/best-snowflake-crm-integration-platforms/)

---

*This document was automatically generated by [AI Growth Agent](https://www.coffee.ai/articles) — AI Growth SEO v4.41.2*
*Generated on: 2026-11-18 04:36:09 GMT+0000*
