- Blog
- Playbooks
How to update your CRM automatically after every call
CRM workflow automation in HubSpot and Salesforce handles the logging. Learn which fields need judgment, and how to update your CRM automatically after calls.
On this page7 sections
Short answer: start your CRM workflow automation with email and calendar logging, then build rules only for fields that follow from another field or a date, like a task when a deal changes stage. The fields your forecast depends on (stage, next step, close date, who signs) come from what was said on calls, so they need something that reads the conversation, with you checking the change before it’s written.
Kate runs sales at a twelve-person startup. At 3pm she had a good call with James. He liked the demo, and then he said three things that changed the deal: his CFO, Jacqui, signs anything at this price, nothing moves until a security review is done, and they can’t start before mid-January.
By 7pm the meeting was logged in HubSpot and a workflow had dutifully created a generic follow-up task. The stage still said Discovery. The close date still said 30 November. The next step still said nothing useful. Friday’s forecast was going to count James’s deal in the wrong month, and Kate was about to spend another evening typing.
This guide draws a line through the middle of that. Some CRM fields can update themselves with a rule. Others only change because of a sentence someone said, and rules can’t hear sentences.
We make Demi, so we’ll be upfront about where it fits and when you don’t need it. Every HubSpot and Salesforce detail below was checked against their own help docs on 12 November 2026. Both ship changes often, so recheck the step you rely on.
Which CRM fields to automate, and which need judgment
Before you build anything, sort your fields with one question: does the new value already exist somewhere as data? If it does, a rule can copy it, stamp it or calculate it. If it only exists in a call or an email, a rule has nothing to copy.
| Field | Comes from | Rule fills it? |
|---|---|---|
| Last contacted | A logged email or meeting | Yes |
| Email and meeting log | Your inbox and calendar | Yes |
| Owner | Territory or rotation | Yes |
| Follow-up task | A stage change | Yes |
| Deal stage | What the buyer agreed to | Needs reading |
| Next step | What you both agreed | Needs reading |
| Close date | Their timeline | Needs reading |
| Who signs | Who they named | Needs reading |
Look at the bottom half of that table. Those are the fields your pipeline report is built on, and they’re exactly the ones a rule can’t touch. It explains why reps with CRM workflow automation switched on still lose evenings to data entry: the clerical half got automated, and the half that needed thinking stayed manual.
The same test, as a flow you can run on any field in your CRM:
Where does the new value come from?
- Another field or a dateA workflow ruleStamp, copy or calculate it
- An email or meeting taking placeActivity loggingHubSpot add-in or Activity Capture
- Something said on a call or in a thread
Can you write the question before the call?
- Yes, one narrow questionAn AI workflow actionHubSpot beta, reads recent transcripts
- No, it depends on the callRead the conversationYou, or an assistant that asks first
CRM workflow automation in HubSpot, step by step
HubSpot’s Workflows come with Professional and Enterprise subscriptions (Sales Hub, Marketing Hub, Service Hub, Data Hub, Smart CRM or Revenue Hub). If you’re on a free or Starter plan, you’ll have the email logging in step 1 but not the workflows in step 2.
Step 1: Log every email without clicking
Connect your work inbox, then install the HubSpot Sales Chrome extension for Gmail or the Office 365 add-in for Outlook. In Gmail, open the sprocket above your inbox, choose Log and track settings and switch on Log email. From then on every email you compose is logged to the matching contact, company and deal.
Three details trip people up:
- A Super Admin can set log and track settings for the whole account, and those override yours.
- The older Outlook desktop add-in is in maintenance mode. HubSpot points Outlook users to the Office 365 add-in.
- When you log an email after the fact, files added with Attach aren’t logged with it.
Missed one? Open the email and click Log email to HubSpot to log it after the fact.
Step 2: Build workflows for the rule-shaped fields
A workflow enrolls records when a trigger fires, then runs actions on them. HubSpot offers five kinds of trigger: filter-based (a property matches), event-based (something happens), schedule-based, webhook-based and manual. The actions that matter for data entry are Edit record, which sets, copies or clears a property on the record or an associated one, and Create task, plus delays and if/then branches.
Three workflows worth building first:
- Stage change creates the task. Enroll deals when the stage becomes Proposal. Create a task for the owner to send it, due in two days.
- Close date in the past. A filter-based workflow enrolls open deals whose close date has passed and creates a task asking the owner to set a real one.
- Copy what’s known. When a deal is created, use Edit record to copy the owner or region from the associated company, so nobody types it twice.
That’s CRM workflow automation doing its job well. Notice what all three have in common, though: they react to a field. None of them knows why the field should change.
Step 3: Try the AI actions, with your eyes open
This is where HubSpot has moved furthest. Its workflow actions now include Data Agent actions, marked beta and paid for with HubSpot Credits. Data Agent: Research can read either the record’s property data or the five most recent call transcripts on that record, answer a prompt you wrote, and return a string, a number or a yes or no. An Edit record action can then write that answer into a property.
It’s real progress, and it’s worth testing on one narrow field, like “Did they mention a competitor?”. Know the limits before you trust it with your forecast:
- You write the question in advance, one per action. “What changed on this call?” isn’t a question a property can hold.
- It reads call transcripts attached to the HubSpot record. A call with no transcript there, or a change that arrived in an email thread, is outside what it reads.
- If no transcript is relevant, it can come back empty.
- Once the workflow runs, Edit record writes the answer. Unless you build a review step yourself, nobody looks first.
Salesforce: Einstein Activity Capture and Flow
Salesforce splits CRM workflow automation across two features. Einstein Activity Capture does the logging, and Flow does the rules.
Step 1: Turn on Einstein Activity Capture
Activity Capture connects your company’s Microsoft or Google account to Salesforce and links email and calendar activity to the right contacts, leads and opportunities. The Standard version is available in Sales Starter, Pro Suite, Professional and Enterprise. An admin connects the accounts and sets the rules, then each rep connects and adjusts their own settings.
The setting to check is Sync Email as Salesforce Activity. With it on, captured emails become ordinary Task and EmailMessage records, so they show up in reports and can trigger flows. From Summer ‘25, Salesforce switched it on automatically for orgs that met its criteria, such as never having used email sync or Inbox. A few things it leaves out by design:
- Internal emails between your own domains aren’t synced.
- Admins can exclude domains, addresses and keywords, and users can block addresses of their own.
- You can choose header-only capture, which keeps sender, recipients and time but drops the subject and body.
Step 2: Use Flow for the rule-shaped fields
Salesforce Flow has dozens of flow types. Three matter for keeping a deal record current:
- Before-save record-triggered flow. Runs when a record is created or updated, before it’s saved, and can change only that record. Salesforce recommends it for field updates because it’s fast. It supports four elements: Assignment, Decision, Get Records and Loop.
- After-save record-triggered flow. Runs once the save is done and can change related records, so this is where you create the follow-up task.
- Schedule-triggered flow. Runs at a set time over a batch of records. Use it for the weekly sweep of opportunities whose close date has passed.
There’s also an Activity-Object Matching Flow, which you can customize to change how captured emails get matched to records.
The pattern is the same as HubSpot’s. Activity Capture gets the email onto the opportunity, and Flow reacts once a field changes. Nothing in that chain decides that a field should change. Even with call recording added on top, the stage on the opportunity still moves when someone moves it.
Why rules can’t keep the deal record current
Go back to Kate’s call. Her record that evening, next to what the call actually implied:
| Field | Rules wrote | The call said |
|---|---|---|
| Last activity | 12 Nov, 3pm | 12 Nov, 3pm |
| Meeting logged | Yes | Yes |
| Stage | Discovery | Proposal |
| Close date | 30 Nov | 15 Jan |
| Next step | Generic follow-up | Security review |
| Who signs | Blank | Jacqui, CFO |
Rules kept 30 November. The call moved the start to January, so Friday's forecast counts this deal a month and a half early.
The top two rows are right because they’re mechanical. The bottom four are wrong because the information arrived as speech. CRM workflow automation did exactly what it was built to do, and the record still lies.
A rule can only react to a field. On a sales call, the deal changes before any field does.
So the gap is specific. Rules move data that already exists. They can’t read a call and decide the next step changed, that a new person now signs, or that the timeline slipped six weeks. Someone has to read the conversation and turn it into field values. For most teams that someone is the rep, at 7pm, from memory.
Every way to update your CRM, compared
| Route | Rule fields | Judgment fields | Plan |
|---|---|---|---|
| By hand | You | You | Any |
| HubSpot Workflows | Yes | No | Pro or Enterprise |
| HubSpot AI actions | Inside Workflows | One set question | Pro, plus credits |
| Salesforce Flow and EAC | Yes | No | EAC from Starter |
| Demi | Left to your CRM | Staged for approval | Free plan |
The best setup for most teams is a combination: your CRM’s logging and a handful of workflows for the clerical half, and something that reads the conversation for the half that needs judgment. Good CRM workflow automation covers the first half so well that the second half is all that’s left to solve.
Where Demi fits
Demi is an AI assistant for your Mac. It doesn’t replace your CRM workflow automation. It handles the fields the rules can’t reach.
It reads where the deal changed
Demi works with HubSpot, Salesforce, Attio, Close and Affinity, and it reads the places deals actually change: your calls (through Gong, Granola or its own notetaker, which listens through your Mac’s audio so no bot joins), your email threads and your calendar. From those it works out which fields a conversation changed. For Kate, that means the stage, the close date, the next step and the person who signs, and it can show you which sentence moved each one.
It stages the change and waits
Nothing is written quietly. Demi lays out each field it wants to change, old value beside new, and holds the change until you approve, edit or skip. If it read something wrong, you fix it before it lands, and the correction teaches it the distinction it missed.
DemiStagedDeal with James
- StageDiscoveryProposal
- Close date30 Nov15 Jan
- Next stepGeneric follow-upSecurity review
- Who signsBlankJacqui, CFO
It catches what went stale, and drafts the follow-up
Your CRM won’t tell you that a next step expired three weeks ago. Demi does: it brings back records whose next step has passed, deals that went quiet, and anything you promised on a call but never sent. The follow-up arrives drafted in your voice, with the promised answer or document already in it, and it waits for your approval too.
So keep both. Your workflows keep creating tasks off stage changes. Demi makes sure the stage changed in the first place.
Demi has a free plan rather than a trial, and you can download it for Mac without a card. New accounts get up to $50 in credits, and paid individual plans start at $25 a month. See how the AI CRM assistant stages an update.
When you don’t need any of this
If you take three or four calls a week, typing the stage and the next step afterwards costs you two minutes, and you’ll remember the call better for doing it. Turn on email logging and skip the rest.
The same goes if your deals move on events rather than conversations: a form submitted, a trial started, an invoice paid. Those are fields changing other fields, and plain CRM workflow automation handles them end to end.
The judgment half only becomes a problem at volume: a rep on six calls a day, a founder selling between everything else, a team whose forecast is built on fields nobody updated. Past that point, the gap between what was said and what the record says starts costing deals.