Sherlock Calls
for PostgreSQL + Tink
PostgreSQL stores your application's core operational data and business records. Tink aggregates bank account and transaction data via open banking. 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 PostgreSQL, Tink simultaneously — read-only, no code changes, no webhooks — and lets you query both with a single Slack message.
- 2
Ask questions that neither PostgreSQL nor Tink can answer alone. PostgreSQL holds every business record your app has ever created — but turning that into an answer requires a developer to write the query. Tink shows financial data — not how it correlates with customer conversations and outcomes. 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 + open banking query
2
Connected platforms, 1 Slack question
0
Code changes or webhooks required
The Investigation Gap
What's invisible when you use PostgreSQL + Tink without Sherlock
Each platform shows you its own data. But the questions that matter most live in the gaps between them.
PostgreSQL financial signals have no corresponding Tink application context
PostgreSQL holds financial health data: payment anomalies, balance trends, cash flow patterns. Tink holds the application records that explain why those patterns exist. Without correlating both, the financial signal is visible but the cause is not.
Tink customer records are worked without the PostgreSQL financial picture
A customer whose PostgreSQL data shows financial distress may appear perfectly healthy in Tink application records. Without joining both, your team works a case with missing evidence — and misses the intervention that would matter.
High-value PostgreSQL financial segments are invisible to Tink product decisions
PostgreSQL identifies customers with strong financial health and expansion potential. Tink holds the product behaviour data. Connecting financial capacity signals to product usage patterns requires a deliberate join that nobody maintains.
Cross-Provider Questions
What teams ask Sherlock about PostgreSQL + Tink
Questions that would take hours to answer manually — answered in under 5 seconds from Slack.
- SC“Which customers have Tink financial stress signals and corresponding unusual PostgreSQL application activity?”
- SC“Show me PostgreSQL records for customers whose Tink payment history shows deteriorating patterns”
- SC“Find Tink financial anomalies and the PostgreSQL application events that occurred in the same window”
- SC“Which PostgreSQL user segments correlate with the strongest Tink financial health profiles?”
- SC“Show me Tink transaction patterns for the customers most active in PostgreSQL this month”
Beta Setup
Connect PostgreSQL + Tink to Sherlock in 2 minutes
No code, no webhooks, no new dashboards. Beta users get direct onboarding support.
- 1
Connect PostgreSQL
Add your PostgreSQL credentials to Sherlock Calls. Read-only access — no code changes, no webhooks, no PostgreSQL configuration required.
- 2
Connect Tink
Add your Tink credentials. Sherlock indexes all open banking transactions, balances, and financial account data automatically.
- 3
Ask your first cross-provider question. The game is afoot.
Type any question about your combined PostgreSQL + Tink 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 + PostgreSQL + Tink
How does Sherlock Calls connect PostgreSQL and Tink data?
- Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries PostgreSQL, Tink 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 PostgreSQL and Tink?
- 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 PostgreSQL + Tink stack?
- You can investigate anything that spans both platforms — table row counts and query latency, financial health signals and cash flow 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 PostgreSQL and Tink 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 PostgreSQL and Tink and is accessed only during an active investigation.
How long does it take to set up the PostgreSQL + Tink 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 + PostgreSQL + Tink
We're accepting a select group of beta users to shape the PostgreSQL + Tink combination. Tell us about your stack and we'll reach out personally if you're a fit.
Explore individual integrations