Sherlock Calls
for Gmail + Google Custom Search
Gmail stores the complete email history of every customer relationship. 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 Gmail, 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 Gmail nor Google Custom Search can answer alone. Gmail holds the richest context — but no one correlates it with call records in real time. 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 productivity + web analytics query
2
Connected platforms, 1 Slack question
0
Code changes or webhooks required
The Investigation Gap
What's invisible when you use Gmail + Google Custom Search without Sherlock
Each platform shows you its own data. But the questions that matter most live in the gaps between them.
Gmail content strategy and Google Custom Search team output are disconnected
Gmail shows which topics drive organic traffic. Google Custom Search holds the documents, meeting notes, and emails your team is producing. Whether your Google Custom Search output aligns with what Gmail says is driving demand is a question most teams never ask.
Gmail search trends surface demand that Google Custom Search content hasn't addressed
Gmail shows rising search queries. Google Custom Search shows what your team has already documented. The gap — topics the market is searching that your team hasn't covered — is high-value and invisible without correlating both.
Google Custom Search institutional knowledge is siloed from Gmail distribution channels
Your team's best insights live in Google Custom Search meeting notes, documents, and emails. The path from that knowledge to content that drives Gmail organic traffic requires a deliberate bridge that most teams never build.
Cross-Provider Questions
What teams ask Sherlock about Gmail + Google Custom Search
Questions that would take hours to answer manually — answered in under 5 seconds from Slack.
- SC“Which Gmail documents are being shared in the same weeks that Google Custom Search shows content traffic spikes?”
- SC“Show me Google Custom Search rising search queries that have no corresponding content in Gmail”
- SC“Find Google Custom Search organic keywords driving significant traffic that aren't addressed in any Gmail document”
- SC“Which Gmail meeting topics align with Google Custom Search search trends that are growing this quarter?”
- SC“Show me the Gmail emails and notes that reference topics currently driving Google Custom Search traffic surges”
Beta Setup
Connect Gmail + Google Custom Search to Sherlock in 2 minutes
No code, no webhooks, no new dashboards. Beta users get direct onboarding support.
- 1
Connect Gmail
Add your Gmail credentials to Sherlock Calls. Read-only access — no code changes, no webhooks, no Gmail 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 Gmail + 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 + Gmail + Google Custom Search
How does Sherlock Calls connect Gmail and Google Custom Search data?
- Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries Gmail, 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 Gmail 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 Gmail + Google Custom Search stack?
- You can investigate anything that spans both platforms — customer email frequency and recency, 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 Gmail 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 Gmail and Google Custom Search and is accessed only during an active investigation.
How long does it take to set up the Gmail + 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 + Gmail + Google Custom Search
We're accepting a select group of beta users to shape the Gmail + Google Custom Search combination. Tell us about your stack and we'll reach out personally if you're a fit.
Explore individual integrations