ClickHouse+HubSpotInvite-Only Beta

Sherlock Calls
for ClickHouse + HubSpot

ClickHouse stores and queries high-volume event and operational data at scale. HubSpot tracks every contact, deal, and touchpoint in your sales pipeline. When you need to investigate across both, the evidence is split between two dashboards neither of which knows the other exists. Sherlock Calls bridges them — no code, no exports, no manual joins. Ask once from Slack and get a sourced answer in under 5 seconds.

TL;DR — What beta users get access to

  1. 1

    Sherlock Calls connects to ClickHouse, HubSpot simultaneously — read-only, no code changes, no webhooks — and lets you query both with a single Slack message.

  2. 2

    Ask questions that neither ClickHouse nor HubSpot can answer alone. ClickHouse holds the raw source of truth — but querying it for business questions requires SQL access and data engineering resources. HubSpot shows pipeline — not which calls or conversations are actually driving it. Sherlock deduces the complete picture from both.

  3. 3

    No dashboard switching, no manual joins, no fog of uncertainty — ask in Slack and receive a sourced answer with evidence from every connected provider in under 5 seconds. The game is afoot.

<5s

Answer to any database + CRM query

2

Connected platforms, 1 Slack question

0

Code changes or webhooks required

The Investigation Gap

What's invisible when you use ClickHouse + HubSpot without Sherlock

Each platform shows you its own data. But the questions that matter most live in the gaps between them.

ClickHouse deal records have no visibility into the HubSpot product behaviour that drives them

ClickHouse holds the sales relationship. HubSpot holds the product usage, event history, and application state. Whether a deal is progressing because of genuine product engagement or because of sales activity alone requires evidence from HubSpot that never surfaces in ClickHouse.

Customer health signals in HubSpot never reach ClickHouse account records

HubSpot may show declining usage, error rates, or feature abandonment — early churn signals. But your ClickHouse account records show a healthy relationship. By the time ClickHouse reflects the problem, retention is already at risk.

ClickHouse pipeline expansion is planned without HubSpot capacity data

Your ClickHouse team identifies upsell opportunities. HubSpot holds the product usage and operational data that shows whether the customer has capacity for expansion. Without the join, upsell conversations happen without the evidence that would make them land.

Cross-Provider Questions

What teams ask Sherlock about ClickHouse + HubSpot

Questions that would take hours to answer manually — answered in under 5 seconds from Slack.

  • SC
    Which HubSpot deal stages correlate with the highest ClickHouse product usage activity?
  • SC
    Show me HubSpot accounts with declining pipeline velocity and their ClickHouse usage trends
  • SC
    Find HubSpot contacts who haven't engaged recently but show high ClickHouse application activity
  • SC
    Which ClickHouse features are most used by HubSpot deals that close fastest?
  • SC
    What's the ClickHouse usage profile of HubSpot accounts at churn risk right now?

Beta Setup

Connect ClickHouse + HubSpot to Sherlock in 2 minutes

No code, no webhooks, no new dashboards. Beta users get direct onboarding support.

  1. 1

    Connect ClickHouse

    Add your ClickHouse credentials to Sherlock Calls. Read-only access — no code changes, no webhooks, no ClickHouse configuration required.

  2. 2

    Connect HubSpot

    Add your HubSpot credentials. Sherlock indexes all contacts, deals, pipeline stages, and activity history automatically.

  3. 3

    Ask your first cross-provider question. The game is afoot.

    Type any question about your combined ClickHouse + HubSpot stack in Slack. Sherlock queries all connected platforms in parallel, correlates the evidence, and returns a sourced answer in under 5 seconds.

FAQ

Common questions about Sherlock + ClickHouse + HubSpot

How does Sherlock Calls connect ClickHouse and HubSpot data?

Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries ClickHouse, HubSpot in parallel, correlates the results by timestamp and shared identifiers, and produces a single sourced answer — the same way a good detective correlates evidence from multiple witnesses.

Do I need to set up any data pipelines between ClickHouse and HubSpot?

No. Sherlock Calls is entirely pull-based — it queries both APIs on demand when you ask a question. There are no webhooks, no ETL pipelines, no data warehouses, and no code changes required in any of the connected platforms.

What kinds of questions can I ask about my ClickHouse + HubSpot stack?

You can investigate anything that spans both platforms — query volume and event ingestion rate, deal velocity and stage conversion rate, cross-platform costs, handoff patterns, and performance comparisons. Sherlock translates your plain-English question into the right API calls and returns the deduced answer.

Is my ClickHouse and HubSpot data stored by Sherlock?

No. Sherlock Calls queries your data in real time and returns results directly to Slack — nothing is stored, indexed, or replicated in any Sherlock database. All data remains in ClickHouse and HubSpot and is accessed only during an active investigation.

How long does it take to set up the ClickHouse + HubSpot integration?

Elementary — typically under 5 minutes total. Connect each platform with read-only credentials, install the Sherlock Calls Slack app, and ask your first question. No engineering, no dashboards, no onboarding calls required.
Invite-Only Beta · Limited spots

Apply for early access to Sherlock + ClickHouse + HubSpot

We're accepting a select group of beta users to shape the ClickHouse + HubSpot combination. Tell us about your stack and we'll reach out personally if you're a fit.