Plug into your revenue stack.

Native two-way integration. When an identified visitor matches a HubSpot contact, we enrich the record with visit data, lead score, pages viewed, and device details. For new visitors, you control whether Knock2 creates a new contact automatically (via a workflow trigger) or routes them to a list for review.

Record source, source detail, lifecycle stage, and contact owner are all configurable in the integration settings. Knock2 doesn't consume your HubSpot enrichment credits.

Native integration with per-user OAuth. Each rep connects their own Salesforce credentials so attribution and record ownership stay correct. Identified visitors can be created as leads or contacts, associated with existing accounts, and deduplicated against your existing CRM data.

Account matching uses domain and company name. You can filter out active customers, open opportunities, or any CRM stage so Knock2 only surfaces new-business signal.

Knock2 connects natively to HubSpot, Salesforce, Attio, Slack, Microsoft Teams, Apollo, Outreach, Lemlist, Instantly, HeyReach, Smartlead, Amplemarket, Unify and Meta Ads. Webhooks cover Clay, Zapier, Make, n8n and anything else that accepts them, and the Knock2 API covers the rest.

Many teams without a CRM run Knock2 with just Slack and a spreadsheet: high-intent visitors go to a Slack channel, and everything else gets logged for follow-up.

Yes. Notifications are filter-driven, so you only get alerts for visitors that matter. Most teams set a lead score threshold (for example, anyone above 75) or a page-visit filter (pricing page, demo page, specific product pages) to ensure Slack only fires on high-intent signal.

Below that threshold, visitors flow into your CRM or a dashboard view for batch review instead of live alerts.

No. Knock2 operates on its own credit pool and doesn't touch enrichment credits from HubSpot, Apollo, Clearbit, or any other tool. When Knock2 pushes data to your CRM, it's writing contact records directly using our own identification and enrichment pipeline.

Yes. Knock2 is built on the same class of identity and analytics technology already running on most B2B websites.

Person-level identification runs on US traffic only, by design. Everywhere else, Knock2 returns company-level information only. That is how it stays within GDPR, CCPA and ePrivacy expectations. The identity data itself is licensed from established data providers.