Sherlock Calls
for ClickHouse + Google Calendar
ClickHouse stores and queries high-volume event and operational data at scale. Google Calendar holds the scheduled meetings and events behind every business relationship. 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 Calendar 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 Calendar can answer alone. ClickHouse holds the raw source of truth — but querying it for business questions requires SQL access and data engineering resources. Google Calendar shows meeting history — not how meetings correlate with call outcomes or deal velocity. 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 + productivity query
2
Connected platforms, 1 Slack question
0
Code changes or webhooks required
The Investigation Gap
What's invisible when you use ClickHouse + Google Calendar without Sherlock
Each platform shows you its own data. But the questions that matter most live in the gaps between them.
Google Calendar business context is never brought alongside ClickHouse data queries
The decisions, commitments, and customer context documented in Google Calendar — meeting notes, email threads, shared documents — are invisible when your team queries ClickHouse. They work the data without the story that explains it.
ClickHouse anomalies have no corresponding Google Calendar documentation trail
When ClickHouse data shows an unexpected pattern — a sudden drop in a key table, an unusual event spike — the Google Calendar context that would explain it (a meeting decision, a product change, an email thread) is never surfaced alongside the raw data.
Decisions made in Google Calendar affect ClickHouse data but are never connected
Strategic decisions discussed in Google Calendar meetings or email threads often produce downstream ClickHouse data changes. But those two events — the decision and its data consequence — are never explicitly linked, making post-hoc analysis guesswork.
Cross-Provider Questions
What teams ask Sherlock about ClickHouse + Google Calendar
Questions that would take hours to answer manually — answered in under 5 seconds from Slack.
- SC“Which Google Calendar decisions from meeting notes correspond to ClickHouse schema or data changes this quarter?”
- SC“Show me ClickHouse anomalous records and the Google Calendar team context — emails, notes — from the same period”
- SC“Find Google Calendar emails referencing data issues that correspond to ClickHouse table changes in the same window”
- SC“Which ClickHouse data events have no corresponding Google Calendar team communication or documentation?”
- SC“Show me Google Calendar meeting decisions that affected ClickHouse business data but have no corresponding audit trail”
Beta Setup
Connect ClickHouse + Google Calendar 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 Calendar
Add your Google Calendar credentials. Sherlock indexes all calendar events, attendees, and free/busy scheduling data automatically.
- 3
Ask your first cross-provider question. The game is afoot.
Type any question about your combined ClickHouse + Google Calendar 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 Calendar
How does Sherlock Calls connect ClickHouse and Google Calendar data?
- Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries ClickHouse, Google Calendar 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 Calendar?
- 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 Calendar stack?
- You can investigate anything that spans both platforms — query volume and event ingestion rate, meeting frequency and attendee patterns, 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 Calendar 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 Calendar and is accessed only during an active investigation.
How long does it take to set up the ClickHouse + Google Calendar 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 Calendar
We're accepting a select group of beta users to shape the ClickHouse + Google Calendar combination. Tell us about your stack and we'll reach out personally if you're a fit.
Explore individual integrations