AI agents trained on HubSpot + Zendesk data
HubSpot holds your sales history; Zendesk holds your support history. Together they show what happened before and after each hand-off, which is the context AI companies want when they train agents that work across systems.
Get matched with buyersFree. No obligation. You approve every step.
We may earn a referral fee from buyers we list. Buyers, not us, pay you, and fees can affect which offers we show. See how we make money.
What happens between HubSpot and Zendesk today
Zapier publishes 1 named template connecting these two apps (Zapier integration page). In plain terms, the most common hand-offs are:
- A new HubSpot Form Submission creates a Zendesk Ticket.
On the HubSpot side the trail runs through Contact, Form Submission, Line Item, Deal; on the Zendesk side through Ticket, Comment, Organization, View.
Beyond this pair, Zapier users most often connect HubSpot to Mailchimp, Airtable, Gmail, and Zendesk to Google Forms, Google Sheets, Slack.
What an agent trained across both could do
Each of these needs records from both systems at once:
- Account health. An agent that combines Zendesk Ticket volume with HubSpot Contact history so owners see risk before renewal.
- Upsell signals. An agent that spots Zendesk Ticket records that mention new needs and creates HubSpot Deal entries for sales.
- One customer timeline. An agent that merges HubSpot Contact and Zendesk Ticket history into one timeline per customer.
Why buyers pay more for linked histories
Zendesk records explain the outcome of HubSpot records, and the reverse. That cause and effect is what single-system data lacks. SourceX says it prefers many in-scope systems: a complete application list of five or more, with at least three needed to submit (SourceX seller guidance).
Side by side
| HubSpot | Zendesk |
|---|---|
| Contact | Ticket |
| Form Submission | Comment |
| Line Item | Organization |
| Deal | View |
| Product | File |
| Invoice | Ticket Comments |
| Engagement | - |
| Payment | - |
| Quote | - |
| List | - |
| Email Subscription | - |
| - |
Buyers that want either side
Buyers that license crm and sales records or customer support history, quoted as published.
micro1 buyer
- What they buy
- “Operational records: SOPs, process docs, knowledge bases, internal comms, CRM and support history”
- Size fit
- 30+ employees
- Closed companies
- Yes: “Separate program for defunct companies”
- Payout as published
- “$100K–$3M+ (marketed range for approved data packages)”
SourceX buyer
- What they buy
- “Support conversations, CRM, engineering and workflow histories”
- Size fit
- 50+ full-time employees at peak
- Closed companies
- Yes: “Operating, acquired and wound-down companies can qualify”
- Payout as published
- “Up to $4M (SourceX says this is an upper bound for the largest datasets, not typical)”
Replay buyer
- What they buy
- “Code and commits, decision threads, financial records, product logs, CRM”
- Size fit
- 20+ employees (lowest band shown)
- Closed companies
- Not published
- Payout as published
- “Shows bands by headcount (20–50, 50–250, 250+); see Replay's page”
AfterQuery buyer
- What they buy
- “Records of how teams work across email, chat, tickets, CRM, finance and industry systems”
- Size fit
- Not published
- Closed companies
- Not published
- Payout as published
- “Not published (terms proposed after reviewing a sample)”
Ventra broker
- What they buy
- “Email, chat, tickets, CRM, documents; CAD, video and game files”
- Size fit
- 30+ staff in US, UK or Canada (reported)
- Closed companies
- Not published
- Payout as published
- “$100K–$2M potential deals (reported by AI Data Payout)”
Buyer terms are quoted from each program's published page as of 2026-11-16; we don't edit them. How we check them: methodology.
What to strip before licensing
- Customer and prospect names, emails and phone numbers (PII) are removed or tokenised.
- Call recordings and transcripts are de-identified; consent rules for recorded calls are checked.
- Payment card numbers or bank details pasted into notes are stripped.
- Personal notes about individuals that are not business records are excluded.
- Customer names, emails, phone numbers and addresses (PII) in tickets are removed or tokenised.
- Payment card or bank details pasted into conversations are stripped.
- Attachments such as IDs, photos or medical documents are excluded unless de-identified.
- Internal notes naming staff can be pseudonymised.
- Buyers de-identify records before training, and you can ask for their method in writing.
- An NDA is signed before any sample leaves your systems.
- You approve the data scope: which systems, which years and which fields.
What it could be worth
- micro1's own estimator API returns about $184,925 for a US company with 30 employees and 3 years of records, and about $239,192 at 50 employees and 5 years (low end of its range). Published calculator output (low end), not a quote Source: micro1 data estimate.
- SourceX's public estimator starts at $50,000 for 50-99 employees and $100,000 for 100-999 employees (low end of each band); 50+ peak full-time employees required. Published band (low end) Source: SourceX estimator.
Buyers price the company's whole dataset: how many systems, how many years and how many people produced it, not a single app. No per-app price exists, and these figures are not a quote or a guarantee.
Sources
- Zapier: HubSpot + Zendesk integrations
- Zapier: HubSpot
- Zapier: Zendesk
- micro1 data estimate
- SourceX estimator
- SourceX seller guidance on in-scope systems (no public URL; summarised)
FAQ
Which HubSpot and Zendesk records connect?
Mostly Contact and Form Submission records in HubSpot, and Ticket and Comment records in Zendesk. The agent jobs above (account health, upsell signals, one customer timeline) show how they combine.
Do I need both HubSpot and Zendesk to sell data?
No. Either can be licensed alone, but buyers price the whole company dataset, so linked HubSpot and Zendesk history is usually worth listing together.