Sales workflow · Granola to Salesforce
Turn Granola meeting notes into Salesforce updates you control
After a meeting, ZeroTwo reads the notes and maps what was said to deal stage, contacts, competitor and next steps. It writes directly by default, or queues each change for your approval in review mode.
- “NDA is signed, moving to a technical evaluation.”Stage
- “Also looking at Acme Corp.”Competitor
- “I'll send the security questionnaire by Friday.”Task
Illustrative example with made-up names.
One meeting, field by field
Every proposed change should be traceable to a sentence in the notes. This is the shape of what you would review.
Meeting header the run starts from
Meridian Health · platform evaluation · Tue Mar 11 · 2:00 PM PT
Open opportunity: Meridian Health – Platform (stage Discovery, Amount $150,000)
| Quote from the notes | CRM field | Old value | Proposed value | Outcome |
|---|---|---|---|---|
| “NDA is signed and we're moving to a technical evaluation.” | Opportunity stage | Discovery | Evaluation | Needs a personStage changes move forecasts. Apply only if your Evaluation criteria say a signed NDA plus a technical evaluation. |
| “Budget is around $150K, maybe $180K if they add the second site.” | Amount | $150,000 | Unchanged | Needs a personA hedged number is not a figure to overwrite. The range goes in the call summary and a person decides. |
| “Priya Nair, VP of Operations, owns this. Marcus Cole from IT joins next time.” | Contacts | None on the deal | Priya Nair (VP Operations), Marcus Cole (IT Director) | ApplyNames and titles are stated outright in the notes. |
| “We're also looking at Acme Corp.” | Competitor | Empty | Acme Corp | ApplyA named vendor in a direct statement. |
| “I'll send the security questionnaire by Friday.” | Task and next step | None | Send security questionnaire, due Fri Mar 14 | ApplyFriday is resolved from the meeting date above. If the notes carry no meeting date, that resolution is a guess, so queue it. |
Illustrative example. The company, people, quotes and figures are made up to show the shape of a review, not output from a recorded run. “Needs a person” is how we would set up the stage and Amount rows; whether a field is applied or queued is your setting.
Where automated CRM updates go wrong
Three cases decide whether you can trust it with a live pipeline.
The same meeting arrives twice
A regenerated or re-sent note repeats every quote, so nothing in it is new. The right outcome is no new contacts, no second task and no second activity entry. We have not published a test of this, so run it on a sandbox record before you trust it (see the checklist).
No matching opportunity
ZeroTwo flags meetings that do not match an existing opportunity. You choose during setup whether it creates a new opportunity or just notifies you. Creating records on a guess is the riskier setting.
The note is wrong
ZeroTwo works with what Granola provides. A misspelled name or a wrong number in the notes carries through to Salesforce, so the first weeks are the time to read what it proposes.
Write directly or review first
The default is a direct write. Review mode is the option you turn on, and for consequential fields it is the one we would start with.
Direct write
DefaultZeroTwo writes to the Salesforce fields you allowed during setup: deal stage, contacts, next steps and activity notes.
Pick it for low-stakes fields such as activity notes and tasks, once you have seen the proposals match what you would have typed.
Review mode
OptionalZeroTwo queues every proposed change for your approval instead of writing it.
Pick it for stage, Amount, new contacts and new opportunities, and for the first couple of weeks of any setup.
Typing it yourself versus a mapped update
A week of back-to-back calls is where manual entry breaks down. A rep takes six calls on Tuesday and intends to update Salesforce later. By the Thursday review, the budget is half-remembered: was it $150K or $180K? This is a scenario, not a statistic.
| Dimension | Typing it yourself | With ZeroTwo |
|---|---|---|
| CRM data freshness | Updated days later from memory, if at all. | Updated after each meeting's notes exist, not at the next pipeline review. |
| Typing into the CRM | Batched at the end of the day and rebuilt from memory. | None by default. With review mode on, you approve or skip each proposed change instead. |
| What the fields reflect | Whatever the rep remembered to enter. | What the notes say. That is only as good as the notes: a misheard name or number is carried into the CRM. |
| Follow-up tracking | Commitments live in someone's head until they slip. | Tasks created from commitments in the notes, with relative dates like Friday resolved from the meeting date. |
What happens after a meeting ends
Reads the notes from the finished meeting
The trigger is a completed Granola meeting. The notes are the only input, so what Granola did not capture cannot be updated.
Maps statements to the fields you allowed
It matches the meeting to an opportunity, then maps statements to your field list and stage definitions. You set both during setup.
Writes the changes, or queues them for review
Stage, contacts, competitor, next step and follow-up tasks go to the deal record, and the call summary goes to the activity timeline.
Five checks before you let it write to a live pipeline
We have not published measured results for this workflow, so run these on a sandbox record and judge it yourself.
Replay one old meeting twice
On a sandbox record, send the same notes twice. Count contacts and tasks afterwards.
Feed it a hedged number
Use a note like the $150K-or-$180K line above. Amount should not change.
Use a relative date with no meeting date
Friday should be resolved from a known date or queued, never guessed.
Send a meeting for an account with no open deal
Expect a flag or notification. A new opportunity should appear only if you turned that on.
Turn on field history before the first real run
Salesforce Field History Tracking keeps a history of changes to the fields an admin selects, up to 20 per object. Salesforce Help: Track Object Field History, read October 2026.
A starting prompt with guardrails
Paste this into the Work agent, then change the field list to match your CRM. It needs the Work agent, which comes with Plus ($14.99/month) and above; see pricing. Connector availability changes, so confirm Granola and Salesforce are available in your workspace on the connectors page first.
After each Granola meeting, read the notes and propose updates to the matching Salesforce opportunity: stage, contacts, competitor, next step, and follow-up tasks for anything I committed to.
Quote the sentence each change comes from.
Resolve relative dates such as "Friday" from the meeting date and time zone. If the notes have no meeting date, ask me.
If a number is hedged or given as a range, do not change Amount. Put it in the call summary and flag it.
If the meeting does not match exactly one open opportunity, do not create one. Tell me instead.Run it after each meeting, or schedule it with scheduled tasks.
Questions before you connect your CRM
Does ZeroTwo write to my CRM by default?
Yes. By default ZeroTwo writes directly to the Salesforce fields you allow during setup: deal stage, contacts, next steps and activity notes. If you would rather it only suggest changes, turn on review mode and each update is queued for your approval.
What if Granola captures something incorrectly?
ZeroTwo works with whatever Granola provides. If a name is misspelled or a number is wrong in the notes, that error carries through to the CRM. Review what it proposes, correct it in Salesforce, and treat better notes as better CRM data.
What happens when two meetings with the same account land on the same day?
Each meeting is processed independently, and later updates build on earlier ones rather than overwriting them. Re-running the exact same meeting is a different case that we have not published a test for, so try it on a sandbox record first.
How does ZeroTwo decide when to change the deal stage?
It maps meeting content to your stage definitions. If the notes mention a signed NDA and a technical evaluation, and your criteria define that as Evaluation, it moves the stage. You define the criteria and it applies them. Because a stage change affects forecasts, review mode is the sensible setting for that field.
What happens if there is no existing deal for a meeting?
ZeroTwo flags meetings that do not match an existing opportunity. You can configure it to create a new opportunity automatically or just notify you so you can decide.
Can I undo a change it made?
We do not document a one-click rollback here. In Salesforce, an admin can turn on Field History Tracking for the fields ZeroTwo writes, which records changes to the selected fields so you can see the previous value and restore it by hand.
Does this work with HubSpot or only Salesforce?
HubSpot is in ZeroTwo's connector list next to Salesforce, and field mapping is set up separately for each CRM. The example on this page uses Salesforce. Check the connectors page for what is available in your workspace.
How fast is it?
We have not published a measured timing for this workflow, so this page makes no speed promise. It depends on when Granola finishes the notes, how many fields are mapped and how quickly your CRM responds.
What plan does this need?
It runs in the Work agent, which is included from the Plus plan ($14.99/month) upward. The Free plan does not include the Work agent. See the pricing page for current plans.
Related workflows
Need the follow-up email and a leadership summary as well? That workflow starts from a call transcript and covers the whole post-call package.
Handle what comes after a phone call, from the commitments made to the message that goes out.
The other side of the meeting: a brief with the account's history in hand before you join.