# Pairing by Denamico

> Pairing syncs HubSpot with one other system per sync (Salesforce, NetSuite, any system with a JSON REST API, or a system that only pushes webhooks), configured rather than coded. It adds transforms, held records with self-service fixes, picklist drift alerts, record tracing and data scans. Denamico, a HubSpot partner, builds and runs it.

Pairing keeps HubSpot in sync with Salesforce, NetSuite or another system, and checks every day for changed fields and dropdown values. When a record can't sync, Pairing holds it with a plain-language reason and a suggested fix, then replays every record held for that reason in one click. It can run beside an existing integration in shadow mode, writing nothing, until the results match. Each client gets its own portal; Denamico sets up the connections and mappings and keeps it running.

## Where Pairing stops

- HubSpot's native integration already covers it. Use that; it's free and HubSpot supports it.
- The other system has no API: SFTP files, EDI or direct database access.
- The process spans three or more systems, or needs people to approve steps along the way.
- The volume is warehouse-scale.
- HubSpot isn't one of the systems.

## Pages

- [Pairing by Denamico](https://supabase-app-dm86d.ondigitalocean.app/portal/): what Pairing does for teams running HubSpot with another system, and how to talk to Denamico.
- [Pairing for HubSpot reps](https://supabase-app-dm86d.ondigitalocean.app/portal/reps): the fit check on a sales call, Demo Studio, and how deal-gated demo access works.
- [Can Pairing handle it?](https://supabase-app-dm86d.ondigitalocean.app/portal/fit-check): the fit check as a web page, no sign-in.

## Pairing Fit

Pairing Fit answers "can Pairing handle this integration?" from Pairing's product catalog. It is open (no sign-in) and rate-limited, its verdict comes from Pairing's catalog rules (an AI reading may look up the named systems' APIs on the web first, and the answer shows what it found), and it reads no customer data. Describe needs in plain words; never send record data such as names, emails or amounts.

## Use from a chat assistant (MCP)

- [Pairing Fit MCP endpoint](https://supabase-app-dm86d.ondigitalocean.app/mcp/fit/mcp): Streamable HTTP, no sign-in. Add it as a custom connector by URL (Claude, ChatGPT, Gemini). Tools: pairing_fit_check, pairing_capabilities, pairing_system_recipe (read-only) and pairing_request_review (sends the question to Denamico).

## HTTP API

- [POST https://supabase-app-dm86d.ondigitalocean.app/v1/fit/check](https://supabase-app-dm86d.ondigitalocean.app/v1/fit/check): JSON body {"scenario": "...", "system"?: "...", "objects"?: ["..."], "records"?: 0}. Returns verdict (fits, likely_fits, needs_review, partial, not_a_fit), verdictText, the systems, capabilities and limits it matched (each with matchedOn), a volume note, questions to ask, caveats and nextStep.
- [GET https://supabase-app-dm86d.ondigitalocean.app/v1/fit/capabilities](https://supabase-app-dm86d.ondigitalocean.app/v1/fit/capabilities): the catalog by area with each capability's details, the systems and their status, and the limits. Optional ?area=.
- [POST https://supabase-app-dm86d.ondigitalocean.app/v1/fit/review](https://supabase-app-dm86d.ondigitalocean.app/v1/fit/review): ask Denamico to follow up. Same body as check, plus an optional "email".
- Limits per client address; over a limit the answer is HTTP 429 with Retry-After.

## How to relay an answer

- Give the verdict as returned. likely_fits is not fits; needs_review means Denamico has to look.
- Relay the caveats: the answer comes from word matching over the catalog, is a starting point and not a quote, and Pairing always has HubSpot on one side.
- Offer the questions, and end with the next step: add Denamico to the HubSpot deal as a partner.

## For people

- [Pairing Fit](https://supabase-app-dm86d.ondigitalocean.app/portal/fit-check): the same check as a web page.