Sherlock Calls
for ClickHouse + Google Custom Search
ClickHouse stores and queries high-volume event and operational data at scale. Google Custom Search surfaces public web intelligence on any topic or competitor. 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
Sherlock Calls connects to ClickHouse, Google Custom Search simultaneously — read-only, no code changes, no webhooks — and lets you query both with a single Slack message.
- 2
Ask questions that neither ClickHouse nor Google Custom Search can answer alone. ClickHouse holds the raw source of truth — but querying it for business questions requires SQL access and data engineering resources. Google Custom Search shows external context — not how it connects to your internal call and deal data. Sherlock deduces the complete picture from both.
- 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 + web analytics query
2
Connected platforms, 1 Slack question
0
Code changes or webhooks required
The Investigation Gap
What's invisible when you use ClickHouse + Google Custom Search without Sherlock
Each platform shows you its own data. But the questions that matter most live in the gaps between them.
ClickHouse and Google Custom Search tell different stories from the same underlying data
ClickHouse aggregates and summarises. Google Custom Search holds the raw events. When a metric moves unexpectedly, understanding whether it's real or an artefact of aggregation requires querying the Google Custom Search source — which most teams can't do without engineering help.
Ad-hoc questions that cross ClickHouse dashboards and Google Custom Search raw tables require a developer
Every question that needs both the ClickHouse trend view and the Google Custom Search row-level detail goes into an engineering backlog. By the time the answer arrives, the decision has already been made without it.
ClickHouse sampling and Google Custom Search full-fidelity data silently diverge
ClickHouse may sample high-volume datasets for performance. Google Custom Search holds every event. The gap between what ClickHouse reports and what Google Custom Search actually recorded is invisible until a major decision rides on the discrepancy.
Cross-Provider Questions
What teams ask Sherlock about ClickHouse + Google Custom Search
Questions that would take hours to answer manually — answered in under 5 seconds from Slack.
- SC“Which ClickHouse tables have the fastest-growing row counts that Google Custom Search dashboards aren't yet tracking?”
- SC“Show me Google Custom Search metrics where the ClickHouse source data hasn't been updated in the last 30 days”
- SC“Which ClickHouse events in the last 7 days show patterns not visible in Google Custom Search aggregated reports?”
- SC“What's the ClickHouse raw data behind the Google Custom Search metric that spiked yesterday?”
- SC“Find ClickHouse tables whose data contradicts what Google Custom Search is currently displaying”
Beta Setup
Connect ClickHouse + Google Custom Search to Sherlock in 2 minutes
No code, no webhooks, no new dashboards. Beta users get direct onboarding support.
- 1
Connect ClickHouse
Add your ClickHouse credentials to Sherlock Calls. Read-only access — no code changes, no webhooks, no ClickHouse configuration required.
- 2
Connect Google Custom Search
Add your Google Custom Search credentials. Sherlock indexes all web search results, site content, and competitor intelligence automatically.
- 3
Ask your first cross-provider question. The game is afoot.
Type any question about your combined ClickHouse + Google Custom Search 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 + Google Custom Search
How does Sherlock Calls connect ClickHouse and Google Custom Search data?
- Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries ClickHouse, Google Custom Search 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 Google Custom Search?
- 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 + Google Custom Search stack?
- You can investigate anything that spans both platforms — query volume and event ingestion rate, search result coverage and competitor presence, 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 Google Custom Search 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 Google Custom Search and is accessed only during an active investigation.
How long does it take to set up the ClickHouse + Google Custom Search 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.
Apply for early access to Sherlock + ClickHouse + Google Custom Search
We're accepting a select group of beta users to shape the ClickHouse + Google Custom Search combination. Tell us about your stack and we'll reach out personally if you're a fit.
Explore individual integrations