Notes
Granola
Connect your AI to Granola
Sales and customer-success reps, product and project managers, and executives and team leads keep their meetings in Granola, but the decisions, commitments and quotes sit in separate notes and transcripts that take time to reread. AI can find and summarize them in seconds, but only if it respects that notes and transcripts are private to their owners and attendees and never shares them beyond those participants.
Why it matters
Capabilities that matter most for Granola
01
Read-only by design
Popdock exposes Granola notes, attendees, invitees and transcript lines as read-only tools, so AI can search and summarize but never change a meeting record.
02
Private to participants
Notes and transcripts stay with their owners and attendees. The AI only surfaces what the signed-in user can already open.
03
Ready-made meeting jobs
The app store includes prompts for meeting recaps, action item roundups, briefings, transcript search and attendance audits.
03
Meetings joined to your systems
Pair Granola with CRM, helpdesk, email and project tools to match attendees, brief a call or find meetings missing from a record.
Use cases
Example AI Use Cases for Granola
scenario
-
Before a donor call, you check Bloomerang for gifts, interactions, tasks and notes, then dig through Granola for what was said in earlier meetings. Two systems, several screens, and it is easy to skip one and walk in without the full picture.
What popdock provides
--
Give a donor email and how many past meetings to include. It finds the constituent in Bloomerang, gathers their gifts, recent contact, open tasks and staff notes, and adds summaries of past Granola meetings with that person. Gift amounts and dates are quoted as returned and nothing is invented. Read-only: nothing in Bloomerang is changed, and if several constituents share the email it lists them and stops. Granola notes stay with the signed-in user.
Business outcome
---
You walk into the donor conversation knowing their giving, open tasks and what was discussed before, with no records changed in Bloomerang.
scenario
-
Getting ready for a call means paging through old meeting notes, then opening the marketing platform to see whether the person is subscribed, what they are tagged with and which campaigns they are in. With the two kept apart, the context you walk in with is thin.
What popdock provides
--
Give an email address and how many recent meetings to include. It reads the person's latest Granola meetings with title, date, owner and summary, then looks them up in Drip for status, tags, lead score and lifetime value, and lists the campaigns they are in. If one side has no match it still reports the other. Read-only: nothing in Drip is changed, and Granola notes stay with the signed-in user.
Business outcome
---
You start the call knowing what was discussed and what marketing has sent, with up to three talking points and nothing changed in Drip.
scenario
-
Before a customer meeting, you check who is attending, then search Nutshell for each person to find their company, open leads and outstanding tasks. Names are spelled differently across systems, and it is easy to miss someone or the context behind them.
What popdock provides
--
Name the Granola meeting and optionally how many days of closed leads to include. It collects the attendees and invitees, drops your own company's addresses, and matches each to a Nutshell contact by email, falling back to an exact name and saying so. For each match it reports company, leads and open tasks. Read-only: nothing in Nutshell is changed, it stops if the meeting or a contact is ambiguous, and meeting content stays with the signed-in user.
Business outcome
---
You know who is in the room, which company and deals they belong to and what is outstanding, with no CRM records changed.
scenario
-
Before a meeting, nobody knows what each invitee already has overdue or due soon, because finding out means looking up every person in Asana one by one. The meeting starts without anyone knowing who is stretched or what is slipping.
What popdock provides
--
Name the Granola meeting and optionally how many days ahead to look. It reads the invitees, finds each one's Asana user by email, and lists their open tasks split into overdue and due soon, with due date, project and link. People with no Asana account or no open tasks are listed rather than left out. Read-only: it reports only what Asana returns, makes no judgement about performance, and flags results that may be capped.
Business outcome
---
You see each invitee's overdue and upcoming Asana work before the meeting starts, without searching person by person, and nothing is changed.
scenario
-
Reps walk into a meeting not knowing whether the invitees have opened or clicked recent emails. Finding out means looking up each person in the email platform, then their activity and notes, and cross-checking against the meeting invite.
What popdock provides
--
Name the Granola meeting and how many days to look back. It reads the invitees (or attendees if there are no invitees) and looks each one up in Constant Contact, then reports company, job title, activity counts by type, the three most recent campaigns and any prior notes. People with no match or no activity are marked as such. Read-only: nothing is changed in Constant Contact and it does not infer interest the data does not show.
Business outcome
---
You arrive knowing how each invitee has engaged with your email, with talking points drawn only from the real activity.
scenario
-
Preparing for a call means opening the CRM for the contact's deals, actions and notes, then hunting through old meeting notes for what was said last time. Open items get missed when the two are viewed in separate tabs.
What popdock provides
--
Give a contact's email and how many past meetings to include. It reads the OnePageCRM record, open deals, pending actions and notes, then adds summaries of the contact's past Granola meetings, using the transcript only when a summary is empty. If the contact is not in the CRM it still reports the meetings. Read-only: nothing in OnePageCRM is changed, it stops if several contacts match, and nothing is quoted that was not returned.
Business outcome
---
You go into the next conversation knowing the deals, open actions and past discussions, with talking points taken from unresolved items.
scenario
-
Before an account meeting, a rep opens Salesforce for contacts, opportunities and cases, then opens Granola to find earlier meetings with each person. Pieced together by hand, the history is patchy and open cases get missed.
What popdock provides
--
Give an account name and how many days back to look. It finds the Salesforce account, lists its contacts, and finds their recent Granola meetings by email, summarising the latest three. It adds open opportunities with stage, amount, close date and next step, and open cases. If several accounts match it lists them and stops, and if there is no history it says so rather than guessing. Read-only: nothing in Salesforce is changed.
Business outcome
---
You walk into the account meeting with contacts, past discussions, open deals and open cases in one place, and nothing changed.
scenario
-
Action items from a meeting live in the notes, and nobody checks them against the task tracker afterwards. Commitments are made on the call but never become tasks, and you only find out when someone asks where it is.
What popdock provides
--
Name the Granola meeting and optionally an Asana project. It pulls the action items and owners from the meeting summary, using the transcript only when the summary is thin and marking those items as inferred. It searches Asana for a matching task for each and reports tracked items with assignee, due date, status and link, and untracked ones. Close name matches are marked as possible. Read-only: it creates and changes no Asana tasks, and owners and dates are never invented.
Business outcome
---
You see which meeting commitments already have a task and which do not, so nothing agreed on the call goes untracked.
scenario
-
To see whether people from a meeting are in the email system, you copy each address from the notes and search for it one by one. It is slow, and you can easily miss who is not on a list or has not given permission to be emailed.
What popdock provides
--
Name the Granola meeting and how many days back to look. It takes the attendees, or the invitees when none are recorded, and looks each email up in Constant Contact, reporting whether they exist, their send permission and the lists they are on. It ends with counts of matched, unmatched and not-sendable people. Read-only: unmatched people are reported, not created, and only emails, names and subscription status are shown. It stops if several meetings match.
Business outcome
---
You know who from the meeting can be emailed and who is missing from Constant Contact, without searching address by address.
scenario
-
Someone copies the attendee emails from the meeting notes and searches the marketing platform for each one to see who is subscribed. It is slow, and people get missed or typed wrongly along the way.
What popdock provides
--
Name the Granola meeting and optionally a start date. It lists the attendees and looks up each email in Drip, reporting whether they are a subscriber, their status, tags and lead score. People with no email or not in Drip are marked clearly, and a name that differs between Granola and Drip is flagged. Matching is on email only, it stops if the title matches more than one meeting, and it is read-only, so nothing in Drip is changed.
Business outcome
---
You see in one table who from the meeting is a Drip subscriber and in what state, with no address by address searching.
scenario
-
Reps copy attendee emails from meeting notes into Mailchimp one at a time to see who is subscribed. It takes a while, and addresses are missed or typed with different capitalization.
What popdock provides
--
Name the Granola meeting and optionally a Mailchimp audience. It reads the attendees, skips those with no email and lists them as unmatched, then looks each address up in Mailchimp, ignoring case and stray spaces. It reports the audience and status for each person (subscribed, unsubscribed, cleaned or not found) and counts per status. Read-only: nothing in Mailchimp is changed, a differing name is shown as both, and it stops if several meetings match.
Business outcome
---
You see each attendee's Mailchimp status in one table, so you know who can be reached without searching address by address.
scenario
-
What was said on a call and what the CRM deal shows slowly drift apart. The customer mentions a new budget or a pushed out timeline, but the deal stage, amount and close date still show last month's picture, and nobody notices until the forecast is wrong.
What popdock provides
--
Name the Granola meeting. It finds the related HubSpot deal through the external attendees' contacts and company, picking the best name match when several are open and stopping if unclear. It then searches the transcript for price, budget, contract, timeline, competitor and renewal, quotes those lines with the speaker, and compares them with the deal's stage, amount and close date. Suggested corrections are text only: read-only, nothing in HubSpot is changed.
Business outcome
---
You see where the conversation and the HubSpot deal disagree, with quoted evidence, so the record can be corrected by you.
scenario
-
Prospects join calls but never get entered in Salesforce, because nobody compares who attended meetings with what is in the CRM. Finding them means going through each meeting's attendee list and searching Salesforce address by address.
What popdock provides
--
Give how many days to look back and optionally your internal email domain. It lists everyone who attended Granola meetings in that window, groups them by email with the number of meetings and latest meeting title, and drops internal addresses. It checks each email against Salesforce contacts, then leads, and reports those with no match, ranked by meetings attended. People it could not check are kept apart as unchecked. Read-only: nothing in Salesforce is changed.
Business outcome
---
You get a ranked list of people who keep attending meetings but are not in Salesforce, so you can add them.
scenario
-
Fundraisers meet donors and forget to log the contact in DonorPerfect, and nobody can tell which meetings are missing without checking each one by hand against the donor's contact history.
What popdock provides
--
Give the meeting owner's email and how many days to look back. It lists their recent Granola meetings, finds which attendees are DonorPerfect donors, and checks each donor for a logged contact from a day before to three days after the meeting. You get a table of meetings with no logged contact, plus counts of meetings checked, with donors and already logged. Read-only: it never saves anything to DonorPerfect, and meeting notes stay with the signed-in user.
Business outcome
---
You see which donor meetings still need a contact logged, so no donor conversation goes missing from the record.
scenario
-
To find out which people from a meeting already exist in Zendesk, you copy each address from the notes and search for it by hand. People are missed, and support never learns that a meeting included someone it has no record of.
What popdock provides
--
Name the Granola meeting. It merges the attendees and invitees by email, marking who attended and who was only invited, and looks each address up in Zendesk. You get two tables: people known in Zendesk with organization, role and open tickets, and people with no Zendesk user, each with a count. Matching is an exact email match ignoring case, people with no email are listed separately, and it stops if several meetings match. Read-only: it never creates or updates a Zendesk user.
Business outcome
---
You see who from a meeting is already a Zendesk user and who is not, without address by address searching or anyone being added automatically.
scenario
-
People you meet in calls and meetings rarely reach the mailing list, because nobody compares who attended with who is in Constant Contact. Doing it by hand means reading attendee lists, searching Constant Contact for every address, and guessing whether a failed search means the person is missing or the lookup just broke.
What popdock provides
--
Say how far back to look and which email domain is your own, and it lists the external people who attended your Granola meetings, then checks each address in Constant Contact. Your own domain is skipped. You get a table of who is missing with their meetings and last meeting date, plus totals. A failed lookup is marked unchecked, never missing. Nothing is added or changed, and meeting notes stay with the signed-in user.
Business outcome
---
You see which meeting contacts are not on your mailing list, with failed lookups kept apart from real gaps, and nothing is changed.
scenario
-
Calls get held and the people on them never make it into the CRM, because nobody cross-checks meeting attendees against Pipedrive. Doing it by hand means opening each meeting, copying every outside email, and searching Pipedrive one address at a time, with case differences causing false gaps.
What popdock provides
--
Say how far back to look, and optionally a word the meeting title must contain, and it lists the external attendees of your Granola meetings, leaving out people from the meeting owner's own domain. It checks each address in Pipedrive without regard to upper or lower case and ranks the missing people by how many meetings they joined. Attendees with no email are listed separately. Nothing in Pipedrive is changed, and meeting content stays with the signed-in user.
Business outcome
---
The people you keep meeting but never recorded surface in a ranked list, so the CRM can catch up without any record being touched.
scenario
-
Showing that a support ticket was discussed internally means searching meeting transcripts by hand for the customer name or a phrase from the subject. It is slow, and it is easy to quote from memory or read too much into a loose match.
What popdock provides
--
Name the Zendesk ticket and how far back to look, and it reads the ticket, then searches your Granola transcripts for the customer's organization and the most distinctive words in the subject. It also finds meetings the requester attended. You get the ticket summary, the meetings with the speaker and quoted lines, and a verdict on whether it was discussed. It quotes only returned text, reports none found rather than inferring, changes nothing in Zendesk, and keeps meeting content with the signed-in user.
Business outcome
---
You can show whether a ticket was discussed in meetings, with exact quotes as evidence and no guesswork.
scenario
-
Change records drift from what was agreed in meetings, because nobody compares the two. Checking means finding the right calls, reading transcripts for the change number, and turning phrases like next Tuesday into real dates before comparing them with the record.
What popdock provides
--
Give a ServiceNow change number, and optionally a start date, and it reads the change record, then searches your Granola meetings for that number. It reads the newest matching meetings, up to five, and pulls the lines that mention the change. You get what was said per meeting, a list of mismatches in dates, risk, owner and approval, and anything agreed that the record does not show. It stops if the change is missing, states its date assumptions, changes nothing in ServiceNow, and keeps meeting content with the signed-in user.
Business outcome
---
Gaps between a change record and what was agreed in meetings show up before they cause trouble, with date assumptions stated.
scenario
-
Finding where an incident was discussed means searching meeting notes by hand for the number. Decisions made in calls then never reach the ticket review, because nobody connected the two.
What popdock provides
--
Give a ServiceNow incident number, and optionally a start date, and it reads the incident, then searches your Granola meetings for that number. It reads the newest matching meetings, up to five, and quotes the lines that contain the number. You get one section per meeting with date, title, owner, summary and quotes, then the decisions and follow-ups stated. It stops if the incident does not exist, reports no mentions rather than guessing, says how many meetings were left out, changes nothing in ServiceNow, and keeps meeting content with the signed-in user.
Business outcome
---
You get every meeting decision about an incident in one place, from real quotes, without searching notes by hand.
scenario
-
Reps hold meetings but forget to log them in Nutshell, and nobody can tell which ones are missing without putting calendars and the CRM side by side. The comparison is dull, so it rarely gets done and the CRM history has gaps.
What popdock provides
--
Give a person's email and how far back to look, and it lists their Granola meetings, then the Nutshell activities in the same window. It pairs them when they fall on the same day and the titles match, and ignores cancelled activities. You get the unlogged meetings with attendee counts, the logged ones with their Nutshell link, and a count of each. It says plainly that pairing by title and day is a best guess, changes nothing in Nutshell, and shows only meeting content the signed-in user can access.
Business outcome
---
You can see which meetings never reached Nutshell, and the guesswork in the pairing is stated up front.
scenario
-
Marketing cannot easily tell which people who clicked a campaign, or never opened it, sales has already spoken to. Answering means exporting the campaign results and then searching meeting records for each person, one at a time.
What popdock provides
--
Name a Constant Contact campaign and whether you want clickers or people who did not open it, and it finds those contacts. It then checks Granola for each one in recent meetings, up to 100 people. You get engagers with meetings (titles, dates and links clicked) and engagers with none, then counts. If several campaigns match, it lists them and stops. It never resends the campaign, reads only meeting titles and dates, and keeps meeting content with the signed-in user.
Business outcome
---
Marketing sees which campaign engagers sales has already met, and who has had no conversation, without exports or manual searching.
scenario
-
External people turn up in meetings and never get added to the CRM, and nobody checks. Catching them means reading every attendee list, dropping your own colleagues, and searching HubSpot for each outside address.
What popdock provides
--
Say how far back to look and which email domain is your own, and it lists your recent Granola meetings and their attendees, leaving out your own domain. It checks each external address in HubSpot once, even if the person appears in several meetings. You get a table grouped by meeting with email, name, title and date, then the totals checked and missing. It offers to create contacts but never does, and meeting content stays with the signed-in user.
Business outcome
---
You see which meeting attendees are not yet HubSpot contacts, and you decide whether any are added.
scenario
-
Meetings with donors happen, but nobody checks whether the contact was ever logged in Bloomerang, so the constituent history has gaps. Finding them means matching each attendee to a constituent and then scanning their interactions for something dated after the meeting.
What popdock provides
--
Say how far back to look, and optionally whose meetings, and it lists your recent Granola meetings and their attendees. It matches each email to a Bloomerang constituent and checks for any interaction on or after the meeting date. You get the meetings where a constituent attended and nothing was logged, with a one-line reason, and a separate list of meetings with no constituent match. It never writes to Bloomerang, and meeting content stays with the signed-in user.
Business outcome
---
Donor meetings with no logged follow-up are flagged, so gaps in constituent history can be closed.
scenario
-
High-scoring leads in the email platform sit untouched because nobody checks whether they have ever met with the team. Finding them means filtering Drip by lead score and then searching meeting records for each person.
What popdock provides
--
Give a minimum lead score and how far back to look, and it lists active Drip subscribers at or above that score, then checks Granola for each one in recent meetings. You get the leads with no recent meeting, highest score first with tags, then a short list of those who did meet. Inactive subscribers are skipped, leads with no email are counted as skipped, and nothing in Drip is changed. Meeting content stays with the signed-in user.
Business outcome
---
Sales sees which high-scoring leads nobody has met, ready to book, without cross-checking two systems.
scenario
-
Deals quietly go cold and nobody notices until the quarter review. Spotting them means listing open deals, finding each contact's email, and then searching meeting records to see when anyone last spoke to them.
What popdock provides
--
Say how far back to look, and optionally which owner, and it lists the open OnePageCRM deals, then checks Granola for each contact's email in recent meetings. You get the deals with no recent meeting, largest first, with stage, expected close date and the date of the last meeting if there was an earlier one. Contacts with no email are listed separately as not checkable. It changes no deals and adds no actions, and meeting content stays with the signed-in user.
Business outcome
---
Quiet deals stand out, largest first, before they go cold, and nothing in the CRM is touched.
scenario
-
Support and account staff walk into customer calls unaware of the open cases those same people have raised. Preparing means looking up each attendee in Salesforce, reading their cases, and then checking whether the meeting ever touched on them.
What popdock provides
--
Name the meeting, and it finds the Granola meeting by title and reads its summary and attendee emails. It then looks up each attendee's open Salesforce cases by contact email, and can read the newest comment on a case. You get the cases per attendee with number, subject, priority, status, owner and escalation, then whether the meeting summary mentions them and which cases it does not. It stops if several meetings match, matches only on email, never edits Salesforce, and keeps meeting content with the signed-in user.
Business outcome
---
You know which open cases a meeting's attendees have, and which the meeting did not cover, before or after the call.
scenario
-
Overdue tasks get chased without knowing whether recent meetings already covered them. Checking means listing late tasks in Asana and then searching meeting transcripts for each one, so people get nudged about work the team has already talked through.
What popdock provides
--
Say how far back to look, and optionally an assignee's email, and it lists the overdue open Asana tasks, up to 20. For each one it searches your Granola transcripts for the task's key words and records the meeting, the speaker and the exact line. You get each task with assignee, due date and link, either the quoted lines or not discussed, with undiscussed tasks first. Keyword hits are called possible mentions. It changes nothing in Asana, and meeting content stays with the signed-in user.
Business outcome
---
You chase only the overdue tasks nobody has discussed, and see exact quotes for the rest.
scenario
-
Follow-ups go out to meeting attendees who have already unsubscribed, because nobody checks the attendee list against the mailing list first. Doing it by hand means collecting emails from meetings and looking each one up in Drip, then judging what each status means.
What popdock provides
--
Say how far back to look, and optionally a word in the meeting title, and it collects the distinct attendee emails from your Granola meetings. It looks up each one in Drip and reports two lists: Do not email, for anyone whose status is not clearly active, and Not in Drip. The raw status value is shown, and the meetings each person attended. It never changes a Drip record, and meeting content stays with the signed-in user.
Business outcome
---
You know who not to email, and who is not on the list yet, before the follow-up goes out.
scenario
-
Commitments are buried across many meetings, and nobody tracks who promised what. Pulling them together means rereading notes and transcripts for phrases like I will or follow up, then sorting them by person yourself.
What popdock provides
--
Give a date range, and optionally a word the meeting title must contain, and it reads the summaries of your Granola meetings in that range, up to the 25 most recent. It then searches the transcripts for commitment phrases to catch what the summaries missed. You get a table grouped by owner with the action, meeting, due date if stated, and whether it was stated outright or inferred, plus items with no clear owner. It never marks items done, a repeated action is listed once, and meeting content stays with the signed-in user.
Business outcome
---
Everyone's commitments from a stretch of meetings land in one list by owner, with guesses clearly marked as such.
scenario
-
Before a donor meeting, someone opens the Granola notes to see who is attending, then searches DonorPerfect for each person to check what they have given and when they were last contacted. People get missed, and giving history and flags are easy to overlook.
What popdock provides
--
Name the meeting and, if you like, how many months of gifts to review (12 by default). It finds the Granola meeting, combines the attendees and invitees, and matches each email to a DonorPerfect donor. For each match it reports giving totals, gifts in the window, the three most recent contacts and any flags, then lists people not in DonorPerfect. It stops if several meetings or donors match. Nothing in DonorPerfect is changed, and meeting content stays with the signed-in user.
Business outcome
---
You walk into a donor meeting knowing each guest's giving, recent contacts and flags, with nothing in DonorPerfect changed.
scenario
-
Seeing every conversation with a donor means searching Granola for each meeting they were in, then reading the contact log in DonorPerfect. The two rarely line up, so you cannot tell which meetings were ever logged as a contact.
What popdock provides
--
Give a DonorPerfect donor ID and how many days to look back (90 by default). It collects the donor's email addresses from DonorPerfect, finds the Granola meetings they attended or were invited to, and fetches the logged contacts. You get one timeline, newest first, with each meeting marked logged if a contact falls within a day of it. Nothing in DonorPerfect is changed, and meeting content stays with the signed-in user.
Business outcome
---
You see every meeting and logged contact for a donor on one timeline, and spot the meetings nobody logged.
scenario
-
Finding out who skipped a recurring meeting means opening each meeting, then comparing the invitee list with the attendee list by eye. With several meetings it is easy to miss a no-show or someone who joined without an invitation.
What popdock provides
--
Give part of the meeting title and a start date. It finds the matching Granola meetings, compares invitees with attendees by email for each one, and reports no-shows and uninvited attendees per meeting, who most often missed, and the overall attendance rate. Meetings with no invitee records are listed separately and nobody is counted as a no-show there. It notes that a missing attendee may be a recording gap, treats the result as meeting information, not a judgement of individuals, and changes nothing.
Business outcome
---
You get attendance gaps across a recurring meeting in one report, framed as possible recording gaps rather than proof of absence.
scenario
-
Before a call, you scroll through old notes to remember what was agreed last time, what is still open and who promised what. If the history is spread over many meetings, something agreed gets forgotten and the call starts cold.
What popdock provides
--
Give the person's email and, if you like, a topic and how many days to look back (90 by default). It finds the past Granola meetings they attended or were invited to, reads each summary, and checks the transcript for the topic when you give one. You get the history in date order, what was last agreed and left open, commitments from each side treated as unconfirmed, a suggested agenda and three questions to ask. It changes nothing, and the briefing stays with the signed-in user.
Business outcome
---
You start each call knowing what was agreed, what is still open and what to ask, without rereading old notes.
scenario
-
A follow-up mailing after a meeting usually goes to the attendee list, but nobody checks that list against Mailchimp. People who unsubscribed or were cleaned get emailed anyway, and people who were never on the list are easy to mistake for consent.
What popdock provides
--
Give the meeting title and the Mailchimp list name. It finds the Granola meeting, takes each attendee's name and email, and looks up each address on your Mailchimp list. You get three groups: safe to email because they are subscribed, exclude with the reason, and not on the list. Someone missing from the list is never treated as consent, and nobody is added or changed in Mailchimp.
Business outcome
---
Your follow-up mailing reaches only people who are subscribed, with each exclusion explained and no one added by mistake.
scenario
-
Writing up a meeting means rereading the notes and the transcript, then working out what was decided and who owns each action. Decisions and owners get lost, and open questions never make it into the write-up.
What popdock provides
--
Give part of the meeting title and, if you like, a start date. It finds the Granola meeting, lists who attended and reads the transcript to confirm the summary and attribute decisions. You get a short summary, decisions with who made them, action items with owner and due date when stated, and open questions. If several meetings match it stops and asks which one, it never invents actions or owners, and the content stays private to the participants.
Business outcome
---
You get a recap with decisions, owners and open questions in one pass, without rereading notes or inventing anything.
scenario
-
A contact's meetings sit in your meeting notes and their email history sits in Mailchimp. To see how they have engaged you check each separately by email address and stitch the dates together by hand.
What popdock provides
--
Give an email address. It finds the Granola meetings they attended or were invited to, then checks their Mailchimp opens, clicks, unsubscribes, campaigns received and list status. You get one dated timeline labelled Meeting or Campaign, plus two sentences on how engaged they are and whether campaigns came before or after meetings. Emails are matched ignoring case, nothing in Mailchimp is changed, and meeting content stays with the signed-in user. If only one system knows the address, it shows that side.
Business outcome
---
You see a contact's meetings and email activity on one dated timeline, with no changes made in either system.
scenario
-
Finding where a topic came up means opening transcripts one at a time and skimming for the right line. Across dozens of meetings you miss mentions, and it is hard to see how the position changed over time.
What popdock provides
--
Give a word or phrase and, if you like, a speaker and a start date. It searches Granola transcripts, groups the matching lines by meeting, and looks up the title, date and owner of the five meetings with the most hits. You get the totals, a short exact quote with timing for each meeting, and a brief view of how the position changed. Quotes are exact, results capped at 100 lines are flagged as possibly incomplete, and nothing is changed.
Business outcome
---
You find every mention of a topic across meetings in one search, with exact quotes and a clear flag when results may be incomplete.
scenario
-
Leaders cannot sit in every meeting, and reading every set of notes takes more time than they have. Themes that repeat across meetings and decisions made in the room are missed, and follow-ups lose their owners.
What popdock provides
--
Give a start date and, if you like, an end date and a meeting owner's email. It lists the Granola meetings in that range, reads each summary, and reads the transcript where a summary is missing or thin. You get the meetings held, recurring themes, decisions, follow-ups with owners, and meetings with no summary or transcript flagged. It digests at most 30 meetings and says how many were left out. Only what the signed-in user can see is included, and nothing is changed.
Business outcome
---
You catch up on a week of meetings through themes, decisions and follow-ups in one digest, with any cap on meetings stated.
scenario
-
Marketers want to know whether the people in a meeting have been engaging with campaigns, but the guest list is in meeting notes and the engagement is in Mailchimp. Checking each guest by hand is slow, so the warm and cold leads in the room stay unclear.
What popdock provides
--
Give the meeting title and how many days to look back (90 by default). It finds the Granola meeting, merges attendees and invitees by email, and checks each person's Mailchimp campaigns received and opens within the window. You get campaigns received, opens and the most recent campaign opened per person, plus those who received campaigns but never opened. People with no Mailchimp activity are named, not omitted. It stops if several meetings match, matches emails ignoring case, and changes nothing in Mailchimp.
Business outcome
---
You know which meeting guests engage with your campaigns and which received them but never opened, before the follow-up.
scenario
-
Preparing for a customer call means searching Mailchimp for their orders and products, then searching meeting notes for earlier conversations. The two sources are checked separately, so the context behind the next conversation is patchy.
What popdock provides
--
Give the customer's email and, if you like, how many recent orders to show (5 by default). It finds the customer in Mailchimp, reads their recent orders and the products on each, and finds the Granola meetings they attended with their summaries. You get a short brief with two talking points based on both. It never guesses a customer ID, says plainly when there are no orders or meetings, and changes nothing in either system. Meeting content stays with the signed-in user.
Business outcome
---
You go into a customer call knowing what they bought and what was discussed, with talking points drawn from both.
scenario
-
Checking whether people in a meeting have Asana accounts means copying emails out of the meeting notes and searching Asana for each one. Across two systems it is easy to miss someone, or to treat a failed search as a missing account.
What popdock provides
--
Give part of the meeting title. It finds the Granola meeting, combines attendees and invitees by email, marking each as attended, invited only or uninvited attendee, and looks each address up in Asana. You get a table with the Asana user ID, not in Asana, or unchecked when a lookup failed, plus counts. It matches on email only, never by name, stops if several meetings match, flags shared emails, and changes nothing in Asana or Granola.
Business outcome
---
You see who in a meeting already has an Asana account and who needs one, with failed lookups marked unchecked, not missing.
scenario
-
Someone copies attendee emails from meeting notes and searches the CRM one by one. People get missed, or the wrong constituent is matched when only a name is searched.
What popdock provides
--
Give part of the meeting title and, if you like, how many days to look back (30 by default). It finds the Granola meeting, collects attendees and invitees, and matches each email to a Bloomerang constituent, with a second try on primary email. You get a table with name, whether they attended or were only invited, and the Bloomerang name, account number, type and status, or not in Bloomerang, plus counts. It matches on email only, stops if several meetings or accounts match, and never adds or updates records.
Business outcome
---
You see who from a meeting is already a Bloomerang constituent and who is not, matched on email and with nothing changed.
scenario
-
Reps copy attendee emails from meeting notes and search HubSpot for each one, so new contacts slip through without a record and nobody checks their company or lifecycle stage.
What popdock provides
--
Give part of the meeting title and, if you like, how many days to look back (30 by default). It finds the Granola meeting, adds invitees to the attendees, and looks up each email in HubSpot. You get a table with company, lifecycle stage, lead status and owner for known contacts, with unmatched people marked NEW, plus counts. It stops if several meetings match, flags two contacts sharing an email, and never adds or updates HubSpot records.
Business outcome
---
You see which meeting guests are known HubSpot contacts and which are new, so no new contact is missed and nothing is changed.
scenario
-
Reps compare a meeting's attendee list to OnePageCRM by hand, one email at a time. People who were never added to the CRM go unnoticed, and so does the follow-up they need.
What popdock provides
--
Give part of the meeting title and, if you like, how many days to look back (14 by default). It finds the Granola meeting, merges attendees and invitees by email and counts any rows with no email, then looks up each address in OnePageCRM ignoring case. You get a matched table with company, status and owner, a not in CRM list, and counts. It stops if several meetings or contacts match and never adds, updates or deletes anything.
Business outcome
---
You see which meeting guests are in OnePageCRM and which were never added, with nothing in the CRM changed.
scenario
-
After a sales call, you copy each attendee email out of the meeting notes and search Pipedrive one address at a time. Duplicate people slip past, contacts who are not in the CRM go unnoticed, and colleagues get searched for by mistake.
What popdock provides
--
Name the meeting and it finds the matching Granola note, stopping to ask if more than one fits. It takes the attendees, or the invitees if nobody is recorded as attending, and looks each external person up in Pipedrive by email. People on your own email domain are listed as internal. You get a table of matched, missing and internal people with organization, job title and open deals. Duplicates and name mismatches are flagged. Nothing in Pipedrive is changed, and meeting content stays with the signed-in user.
Business outcome
---
You see which meeting attendees are already in Pipedrive and which are missing, with duplicates flagged and no changes made to the CRM.
scenario
-
After a call, you compare the attendee list in your meeting notes with Salesforce by hand. Each person has to be searched as a contact and again as a lead, and people who are not yet records are easy to miss.
What popdock provides
--
Give a meeting title and it finds the Granola note, stopping if more than one note matches. It collects attendees and invitees with their emails, then checks Salesforce for a contact and, if none is found, a lead, matching on exact email and ignoring case. If two records share an email, it lists both rather than choosing. You get a table with the Salesforce name, account or company and owner, plus counts. Nothing in Salesforce is changed.
Business outcome
---
You know who from a meeting is already in Salesforce as a contact or lead and who is missing, without comparing lists by hand.
scenario
-
Checking whether the people in a meeting have ServiceNow accounts means copying emails from your meeting notes into ServiceNow one at a time. Inactive accounts and people with no account at all are easy to miss, especially when emails differ by case.
What popdock provides
--
Name the meeting, and optionally a start date, and it finds the matching Granola note, stopping if the match is ambiguous. It merges attendees and invitees by email, then looks each one up in ServiceNow, ignoring case. You get a table with title, department, active status and VIP flag, followed by the people with no ServiceNow user and any inactive users. Nothing in ServiceNow is changed, and meeting content stays with the signed-in user.
Business outcome
---
You know which meeting participants have active ServiceNow accounts, which are inactive and which are missing, in one pass and with no changes made.
scenario
-
To see whether the people in a meeting are already in the donor database, someone copies emails into DonorPerfect one at a time. Unknown contacts go unnoticed, and a single email that belongs to several donor records is easy to mishandle.
What popdock provides
--
Name the Granola meeting and it checks every attendee and invitee against DonorPerfect by email, falling back to the address records when the donor search finds nothing. You get three tables: matched donors with donor ID and type, people not found, and invitees who did not attend. An email that maps to several donors is flagged with every ID. It stops on an ambiguous meeting, changes nothing in DonorPerfect, and meeting content stays with the signed-in user.
Business outcome
---
You see who from a meeting is a known donor, who is new and who was invited but absent, without changing any donor record.
scenario
-
Checking whether meeting participants exist in the CRM means searching Nutshell for each name. Common names return several people, and unknown contacts go unnoticed, so the CRM drifts from who you actually met.
What popdock provides
--
Name the Granola meeting and it lists each attendee and invitee, marking who attended, who was invited only, or both. For each person it searches Nutshell and confirms the match by comparing emails, flagging a match on name only or an ambiguous name instead of picking one. People on your own domain are left out unless you ask. You get a table with counts per result. Nothing in Nutshell is changed, and meeting content stays with the signed-in user.
Business outcome
---
You see which meeting participants are Nutshell contacts and which are new, with ambiguous names flagged and no records changed.
scenario
-
Before a stakeholder call, you look up each attendee in ServiceNow and then search for their open tickets, one person at a time. It is slow, and an open issue that should have been raised in the meeting gets missed.
What popdock provides
--
Name the meeting and it finds the Granola note, stopping to ask if several match. It takes the attendees, finds each one's ServiceNow user and lists the open incidents they raised as caller, up to the number you choose per person. Resolved, closed and cancelled incidents are left out. You get incidents per attendee, the five highest-priority across everyone, and attendees with no ServiceNow user. Nothing in ServiceNow is changed.
Business outcome
---
You walk into a stakeholder call knowing which attendees have open incidents and which matter most, without searching person by person.
scenario
-
Before a customer meeting, someone copies attendee emails from the meeting notes and searches Zendesk for each one. Open tickets are easy to miss, and a person searched by name can pull up the wrong customer.
What popdock provides
--
Name the meeting and it finds the Granola note, stopping to ask if more than one matches. It takes each attendee's email and finds the tickets they requested in Zendesk, keeping new, open, pending and on-hold tickets and adding solved ones only if you ask. You get a section per attendee with subject, status, priority, assignee and created date, and a plain statement when someone has no tickets. Matching is by exact email only, and nothing in Zendesk is changed.
Business outcome
---
You go into a customer meeting knowing each attendee's open Zendesk tickets, with no guessing by name and no changes to tickets.
scenario
-
Before a call, you dig through the CRM and old notes by hand. Deals, recent activities and earlier notes are in different places, so you arrive without the full picture of where the deal stands.
What popdock provides
--
Name the Granola meeting and, optionally, how many days to look back. It finds the note, stops if several match, and takes the attendees outside your own email domain. It finds them in Pipedrive, then pulls the open deals for their organizations and the recent activities and notes for each person. You get a brief per organization and three short talking points drawn from the meeting summary and the Pipedrive history. It stops if no attendee is in Pipedrive. Nothing is changed, and meeting content stays with the signed-in user.
Business outcome
---
You arrive at the call with open deals, recent activity and talking points in one brief, without opening each record yourself.
scenario
-
Preparing for a customer meeting means opening the CRM for deals, the ticket queue for open issues and old meeting notes for what was said last time, all in separate tabs. Something usually gets left out.
What popdock provides
--
Name a HubSpot company, and optionally how many days of meetings to include, and it finds the company, stopping to ask if several match. It lists the open deals, open tickets with priority and the people on the account from HubSpot. It then finds the past Granola meetings those people attended and reads each summary. You get a briefing under one page with the company snapshot, deals, tickets, meeting history and open questions to raise. Gaps are stated, and nothing in HubSpot is changed.
Business outcome
---
You get one briefing with deals, tickets and past conversations before the call, with any gaps stated instead of hidden.
scenario
-
When a donor mentions a gift or pledge in a conversation, someone has to check it against the recorded transactions by hand. Amounts get re-keyed or compared from memory, so mismatches and unrecorded gifts go unnoticed.
What popdock provides
--
Give a Granola meeting title and the constituent's email. It finds the note, stops if several match, and searches the transcript for lines about gifts, pledges and donations that name an amount. It finds the constituent's Bloomerang account by email and reads their transactions from the 90 days before the meeting. You get a table with each quote, speaker and time, the nearest transaction, and a verdict of matched, amount differs or not recorded. It never guesses amounts and changes no transactions.
Business outcome
---
You see whether what a donor said in a meeting matches what was recorded, with a verdict per mention and no transactions changed.
scenario
-
Tying a conversation to the deals it affects means looking up each attendee in Nutshell and then searching for their leads and their company's leads. It is slow, and a lead tied to a colleague at the same company is easy to overlook.
What popdock provides
--
Name the Granola meeting and, optionally, a lead status such as open. It lists the attendees, matches each to a Nutshell contact by comparing emails, and flags ambiguous names instead of picking one. It then finds the leads linked to each person and their company, removes duplicates and applies your status filter. You get one row per lead with value, close date and owner, plus total open value per currency. Nothing in Nutshell is changed, and meeting content stays with the signed-in user.
Business outcome
---
You see every lead tied to a meeting's attendees and their companies, with open value totalled per currency and no records changed.
scenario
-
A manager reviewing a deal cannot tell whether the buying group has actually met with the team. The opportunity lives in Salesforce, the conversations live in meeting notes, and nobody lines them up until the deal has gone quiet.
What popdock provides
--
Name the opportunity and, optionally, how many days count as stale. It finds the Salesforce opportunity, stopping if several share the name, then reads its contact roles and their emails. It finds each person's Granola meetings and reads the summaries. You get the opportunity stage, amount, close date and next step, a meeting timeline, the roles with no meeting, and a clear stale or active call. The latest summary is compared with the next step. Contacts without an email are listed as untraceable. Nothing is changed.
Business outcome
---
You can tell whether a deal's buying group has really met with your team, and whether the next step matches, without searching two tools.
scenario
-
Reconstructing which meetings happened on a deal means finding the deal's people in Pipedrive, searching meeting notes for each of them, and merging the dates with the logged activities by hand. Gaps in contact are easy to miss.
What popdock provides
--
Give a Pipedrive deal ID and, optionally, how many days to look back. It reads the deal, stopping if nothing is found, finds the people at its organization and collects their emails and the deal's activities. It then finds the Granola meetings those people attended or were invited to and reads each summary. You get one timeline merging meetings and Pipedrive activities, with any gap longer than 30 days noted. If no meetings exist, it says so. Nothing in Pipedrive is changed, and meeting content stays with the signed-in user.
Business outcome
---
You get a single dated timeline of meetings and activities on a deal, with contact gaps called out and no records changed.
scenario
-
Preparing for a customer call means reading the Zendesk history in one place and past meeting notes in another, then stitching the two together by hand. Themes that show up in both are easy to miss.
What popdock provides
--
Name the customer organization and, optionally, how many days to look back. It finds the Zendesk organization, stopping if several match, and gathers its recent tickets. It finds Granola meetings that mention the organization and keeps only those where an attendee's email domain matches the organization, never matching on name alone. You get one brief with the organization details, ticket counts by status and priority, the latest tickets, meeting summaries and themes that appear in both. If one side is empty it reports the other alone. Nothing is changed.
Business outcome
---
You get one brief of a customer's tickets and meetings before the call, with themes that span both and no records changed.
No items found.
Ready to unlock your data?
Start building tools that turn your business systems into AI superpowers
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.