Sherlock Calls
for Google Calendar + Synthflow
Google Calendar holds the scheduled meetings and events behind every business relationship. Synthflow orchestrates no-code voice AI workflows for any use case. 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 Google Calendar, Synthflow simultaneously — read-only, no code changes, no webhooks — and lets you query both with a single Slack message.
- 2
Ask questions that neither Google Calendar nor Synthflow can answer alone. Google Calendar shows meeting history — not how meetings correlate with call outcomes or deal velocity. Synthflow shows workflow metrics — not which calls produce downstream business results. 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 + voice AI query
2
Connected platforms, 1 Slack question
0
Code changes or webhooks required
The Investigation Gap
What's invisible when you use Google Calendar + Synthflow without Sherlock
Each platform shows you its own data. But the questions that matter most live in the gaps between them.
Google Calendar and Synthflow each hold half the picture
Google Calendar shows meeting history — not how meetings correlate with call outcomes or deal velocity. Synthflow shows workflow metrics — not which calls produce downstream business results. Without correlating both, your team sees two incomplete views of the same underlying reality — and every investigation stops at the boundary between systems.
Cross-platform cost and performance remain invisible
Google Calendar tracks its own scheduling coordination time. Synthflow tracks its own workflow run cost. Your true cost per outcome — and the performance of each component in your combined stack — requires data from both, but neither platform shows you that unified picture.
Critical events disappear at the boundary between systems
When a session, contact, or signal moves between Google Calendar and Synthflow, the transition is recorded with different identifiers in each system. Tracing what happens across the full journey requires a manual join that takes hours you don't have.
Cross-Provider Questions
What teams ask Sherlock about Google Calendar + Synthflow
Questions that would take hours to answer manually — answered in under 5 seconds from Slack.
- SC“What's the combined activity across Google Calendar and Synthflow in the last 7 days?”
- SC“Show me events that touched both Google Calendar and Synthflow in the last 24 hours”
- SC“What's our blended cost per outcome across Google Calendar and Synthflow this month?”
- SC“Which Google Calendar sessions had issues that correlate with Synthflow events this week?”
- SC“Compare performance metrics across Google Calendar and Synthflow for the past 30 days”
Beta Setup
Connect Google Calendar + Synthflow to Sherlock in 2 minutes
No code, no webhooks, no new dashboards. Beta users get direct onboarding support.
- 1
Connect Google Calendar
Add your Google Calendar credentials to Sherlock Calls. Read-only access — no code changes, no webhooks, no Google Calendar configuration required.
- 2
Connect Synthflow
Add your Synthflow credentials. Sherlock indexes all voice workflow call logs, outcomes, and step completion data automatically.
- 3
Ask your first cross-provider question. The game is afoot.
Type any question about your combined Google Calendar + Synthflow 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 + Google Calendar + Synthflow
How does Sherlock Calls connect Google Calendar and Synthflow data?
- Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries Google Calendar, Synthflow 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 Google Calendar and Synthflow?
- 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 Google Calendar + Synthflow stack?
- You can investigate anything that spans both platforms — meeting frequency and attendee patterns, workflow completion rate per step, 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 Google Calendar and Synthflow 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 Google Calendar and Synthflow and is accessed only during an active investigation.
How long does it take to set up the Google Calendar + Synthflow 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 + Google Calendar + Synthflow
We're accepting a select group of beta users to shape the Google Calendar + Synthflow combination. Tell us about your stack and we'll reach out personally if you're a fit.
Explore individual integrations