Turn sales call notes into a CRM update and a follow-up email
Starts when a call recorder, notes app or CRM sends call notes. Ends with a CRM-ready update and a follow-up email draft for a person to approve.
Bring the step you are stuck on: 30 minutes, a straight answer and the next step. If you would rather have it built, a reply within 5 working days.
The route
7 steps: 3 rule steps, 1 AI step and 1 person step
Copy, share, discuss
- Copy
Available once this workflow passes its checks.
- Share
todkett.com/automations/sales/call-notes-to-crm/
- Discuss
Opens when the first workflow passes its checks. No GitHub account? Ask about this by form.
How the library, the tracks and the talk work: the community page.
At a glance
- Starts when
- A call recorder, notes app or CRM posts call notes or a transcript to one webhook.
- Input
- Call notes or a transcript arrive, up to 20 calls per request.
- Output
- A CRM-ready update and a follow-up email draft for a person to approve.
- AI
- Uses AIReading the notes, pulling out the deal facts and drafting the follow-up email.
- Rule checks
- 6 checks around the AI
- Tools
- Webhook from a call recorder, notes app or CRM, OpenRouter, Google Sheets
- Last stress test
- No recorded run yet
01Steps
The steps
7 steps: 3 rule steps, 1 AI step and 1 person step. Founder-led sales: the CRM is always a week behind. The hour after every call goes to typing notes and writing the recap email, so next steps slip and the pipeline goes stale.
01Trigger
Call notes arrive
Call notes or a transcript arrive, up to 20 calls per request.
02Rule step
One item per call, capped
One item per call; notes capped at 12,000 characters.
03AI step
AI pulls the deal facts
AI pulls out a summary, MEDDPICC fields, budget, timeline, dated next steps, risks and deal health, and drafts the follow-up email.
04Rule step
Check stage and amount
Rules check the suggested stage and amount, and fill missing due dates.
05Rule step
Ready or needs review
Each call is marked ready to sync or needs review, with reasons.
06Person step
A person approves
A person approves the CRM update and the follow-up email before anything is synced or sent.
07Output
CRM update and email draft
A CRM-ready update and a follow-up email draft.
CRM drafts
02Where AI is used
Where AI is used, and what stays with you
AI reads, judges or drafts. Fixed rules check, decide and route. A person approves anything that goes out.
AI step
Step 03Reading the notes, pulling out the deal facts and drafting the follow-up email.
Call notes are free text. Code, not the model, decides what is safe to sync.
What the model reads
- The call notes or transcript, capped at 12,000 characters.
What it never sees or decides
- The deal stage or the amount: rules check both and flag big changes.
- A closed deal, won or lost: that always needs a person.
- The CRM: nothing is written or sent until a person approves.
Model calls: 1 model call per call.
Fixed rules
They check, decide and route. 3 rule steps.
- 02One item per call, capped
- 04Check stage and amount
- 05Ready or needs review
A person
- 06A person approves the CRM update and the follow-up email before anything is synced or sent.
03Checks
Checks around the AI
What runs before the model, and what checks its answer after, in plain words. Build these into your version too.
- 01The stage must be on the allowed list, otherwise the current stage is kept and flagged.
- 02A jump of more than one stage is flagged for a person.
- 03Closing a deal, won or lost, always needs a person.
- 04An amount change over 25% is flagged.
- 05Next steps without a date get the call date plus 3 days, labeled as a default.
- 06Nothing is written to the CRM or sent: the output is a draft.
04The 8 checks
Stress test
The 8 checks we run on every workflow, and you can run too. A check marked Not needed says why.
- Status
- Not yet0 of 7 that apply have a recorded pass
- Last run
- No recorded run yet
- Model review
- Still open
Checks marked Not yet are still open. 2 of them were seen in the workflow design on 23 Oct 2026; a check shows Passed only once its test run is recorded.
ST7Human sign-off
Status: Not yet
Seen in the workflow design on 23 Oct 2026. The recorded test run is still open.
ST8Rules around the AI
Status: Not yet
Seen in the workflow design on 23 Oct 2026. The recorded test run is still open.
0 passed · 1 not needed · 7 not yet
What we testWe show what we tested, never the test data. The example below is made up.
05Test replay
How to test it
Before you trust a workflow, try to break it. The sample record runs the route step by step. Each break test below gets its own replay once its recorded run exists.
- Record
- CALL-0215
- Data
- Sample run, made-up data
01Call notes arrive
Notes from a Fernway sales call
Done02One item per call, capped
Notes within 12,000 characters
Done03AI pulls the deal facts
Summary, budget, next steps and risks; follow-up drafted
Done04Check stage and amount
One-stage move allowed; undated step gets the call date plus 3 days
Done05Ready or needs review
Marked ready to sync
Done06A person approves
Held for the rep's approval
Waiting for a person07CRM update and email draft
Saved as drafts; nothing synced or sent
CRM draftsArrived
CALL-0215 reached the last station: CRM drafts. Saved as drafts; nothing synced or sent.
Sample run on made-up data. No stress-test run is recorded yet, so this plays the example, not a test. Nothing runs live.
The break tests for this workflow
- ST3Not needed
Same input sent twice
Returns a result only: writes and sends nothing.
- ST2Not yet
Instructions hidden in the input
No recorded run to replay yet.
- ST4Not yet
A connected service fails
No recorded run to replay yet.
- ST8Not yet
The AI returns a broken answer
Seen in the workflow design. No recorded run to replay yet.
06Example
The example, in and out
Made-up data, written to show the steps; no recorded run stands behind it yet. Fernway is a made-up small software company, and its address ends in .example, so it cannot belong to a real business.
InputExample
Example on made-up data: notes from a Fernway sales call with a made-up prospect. Budget agreed, next step send pricing, stage moved from Discovery to Proposal.
OutputExample
Summary, budget, next steps and risks pulled out. A one-stage move is allowed. The next step had no date, so it gets the call date plus 3 days, labeled as a default. Marked ready to sync, with the CRM update and the follow-up email saved as drafts for the rep.
07Limits
When not to automate this
- It never closes a deal or writes to the CRM without a person.
- Follow-up emails stay drafts until a person sends them.
08What you need
What you need to run it
| Tool | Access |
|---|---|
| Your call recorder, notes app or CRM | Post call notes or transcripts to one webhook |
| OpenRouter | One API key with a credit limit, for the extraction step |
| Google Sheets | Optional: write a test log |
- Where it runs
- In n8n, self-hosted or n8n cloud.
- Model calls
- 1 model call per call.
- Running costs
- Yours, paid to each service directly. Scope in writing first. A quote before any build. No prices on the site yet.
How to adapt it
Changes we have made or tested on this workflow.
No tested change is listed yet.
What changed
- ContentFirst version, written from the 23 Oct 2026 catalog.
09FAQ
Questions people ask about it
Does it change my CRM by itself?
No. It returns a CRM-ready update and a follow-up email draft, and a person approves both.
What rules check the deal?
The stage must be on the allowed list, a jump of more than one stage is flagged, closing a deal as won or lost always needs a person, and an amount change over 25% is flagged.
What if a next step has no date?
It gets the call date plus 3 days, labeled as a default so a person can change it.
10Related
Where to go next
Use cases
6 steps
Sales
Turn a deal request into a branded proposal PDF and CRM dealAI in one step only: reading pasted deal notes (chat version only)
8 steps
Can you automate it?
Stuck on your version of this workflow?
Bring the step that does not work. In 30 minutes you get a straight answer and the next step. If you would rather have it built, tell us your tools and the rules you already follow. Scope in writing first. A quote before any build. No prices on the site yet.