Before updating a HubSpot company
Your agent has data it wants to write to a HubSpot company record. Before it does, call Anchord to resolve the company identity and guard the write. If there's a conflict or ambiguity, Anchord blocks the write and escalates to a human — no duplicate created, no wrong record updated.
When to use this
- Your agent is about to create or update a company in HubSpot
- You're syncing data from another system (Salesforce, Stripe, internal DB) into HubSpot
- You want to prevent duplicates that HubSpot's built-in deduplication misses
Endpoints to call
| Step | Endpoint | Purpose |
|---|---|---|
| 1 | POST /api/v1/ingest/batch | Ingest the HubSpot company record |
| 2 | POST /api/v1/resolve/company | Match to a canonical AnchorID |
| 3 | POST /api/v1/guard/write | Evaluate the write before executing |
Expected outcomes
resolved → allowed High-confidence match, write is safe. Your agent proceeds with the HubSpot API call.
not_found → allowed No existing match — a new AnchorID was created. Safe to create the HubSpot record.
needs_review Multiple plausible matches. Do not write. Escalate to the Review Queue for human resolution.
blocked Entity exists but has conflicts or missing links. Do not write. Log the blocks array and escalate.
What the agent should do next
If allowed: Execute the HubSpot API write using the canonical entity ID from Anchord.
If needs_review: Do not write. Store the attempt_id and link the user to the Review Queue. Retry after human resolution.
If blocked: Do not write. Log the audit_id and blocks array. Surface the issue to the user.