Work · Fintech · CRM

The story of a lead is spread across five tools

What I built: Every conversation on one record

Meetings, bookings and two-way LinkedIn on every contact, so a fintech’s sales team sees the whole story in one place.

Same client as the other fintech examples.

4,700+ LinkedIn leads, every reply on the record (verified)

4,700+ leads on LinkedIn (verified) 30.7% acceptance (verified) 15.1% reply rate (verified) 57 bookings synced (verified)

Verified = seen in the system. Self-reported = my own measure.

The story of a lead lived in five tools.

Meeting notes sat in Read.ai. Bookings sat in Cal.com. LinkedIn chats sat in HeyReach. Email sat in Outlook.

Nobody saw the full story of a lead without asking around.

One record now holds every conversation.

• Read.ai meetings to the CRM: creates or updates the company, people, meeting, notes, tasks and opportunity, then checks the deal stage.
• Cal.com bookings to the CRM, as their own records linked to the contact and company.
• HeyReach (LinkedIn), both ways: a rep sends a LinkedIn reply from the CRM; sent messages and replies land on the person as notes; a reply also creates a follow-up task; daily LinkedIn stats.
• Outlook (Microsoft Graph): sales emails go out from n8n, and the reply assistant reads the thread when it’s needed.
• A six-stage pipeline with saved views: By Stage, Stuck deals (30+ days), Pipeline movement (this week).

Step by step

1. Each tool sends an event to n8n when something happens: a meeting ends, a booking lands, a LinkedIn reply comes in.
2. n8n finds the right person and company in the CRM, or creates them.
3. It saves the event on that record as a note, task or meeting.
4. Email threads are pulled in when you reply, not stored on the record.

Screenshots

• A contact’s timeline with meeting notes and tasks.
• LinkedIn replies saved to the CRM.
• Read.ai meetings into the CRM.
• Cal.com bookings into the CRM.
• Bookings as their own records.
• One record, the whole story.
• Saved pipeline views.

How I built it

• I worked inside the team’s own tools: their self-hosted n8n and their self-hosted Twenty CRM.
• I wrote the workflows with Claude Code as my AI coding tool (self-reported). I decided what to build and checked every run.
• Read-only probe workflows tested each API before anything wrote to it.

What you can check

• Verified: 57 Cal.com bookings and 43 meetings in the CRM. Read.ai shows as a lead source on records. Source: CRM UI, 15 Oct 2026
• Verified: HeyReach send, sent, reply and daily-stats workflows run in n8n. Source: n8n, 15 Oct 2026
• Verified: 4,700+ leads reached on LinkedIn. 30.7% acceptance and 15.1% reply rate. Every reply logged in the CRM automatically. Source: HeyReach, May–Oct 2026
• Verified: In detail: 4,761 unique leads contacted. 4,934 connection requests sent, 1,516 accepted. 2,350 messages across 1,327 conversations, 201 replies. 83 of 200 auto-tagged replies were tagged interested (41.5%). 5,990 profile views. Source: HeyReach, May–Oct 2026

Take the workflow, free

• Read.ai meetings to Twenty: Saves Read.ai meetings, notes and tasks on the CRM record.
• Cal.com bookings to Twenty: Saves Cal.com bookings and moves the deal stage.
• HeyReach and Twenty, both ways: Links LinkedIn outreach (HeyReach) and the CRM, both ways.

What this means for your team

Open one record and see the whole relationship: the call, the booking, the LinkedIn thread, the next task. No more asking around.

Tools

• Twenty CRM
• n8n
• Read.ai
• Cal.com
• HeyReach
• Outlook / Microsoft Graph

More like this

• An AI that reads the history and drafts the reply
• Move off your old CRM without losing a deal

Book a free 15-min call · All examples →