Setting up Greg for your CRM
Greg is an AI notetaker from Greg Inc. It joins your Zoom, Google Meet, and Microsoft Teams calls, transcribes them, and writes the summary and action items into your CRM contacts and opportunities. This guide covers installing the app from the Marketplace, what it asks permission for, and what to check if something doesn't look right.
Before you start
- • A CRM account — a single account or an agency that manages several client accounts.
- • A Greg account. Start at getgreg.io — no credit card required.
- • Permission to install Marketplace apps in the CRM account you're connecting.
Installation
- 1
Install the app from the Marketplace
Open the Greg listing in the Marketplace and choose Install. You will be asked which account to install into. Pick a single CRM account, or install at the agency level and select the client accounts you want covered.
- 2
Approve contacts and opportunities access
The Marketplace shows the scopes the app is requesting. These are listed in full below — Greg asks for contact and opportunity access, plus the OAuth scopes that agency installs require. Approving returns you to Greg and the connection is stored against your workspace.
- 3
Confirm the connection in Greg
In Greg, go to Settings → Integrations. Your connected CRM account appears under the CRM section. If you installed at agency level you can pick which account a given workspace writes to.
- 4
Connect a calendar (or paste a meeting link)
Go to Settings → Calendars and connect Google Calendar. Greg then sees your upcoming Google Meet, Zoom, and Microsoft Teams calls and can join them automatically. You can also paste a meeting link at any time to have it join a one-off call.
- 5
Run a meeting
The Greg notetaker joins the call, records it, and transcribes it with speaker labels. When the meeting ends it writes an AI summary with key points and action items.
- 6
Check the CRM
Greg matches the meeting to a CRM contact and writes the summary as a note on that contact. Where an opportunity exists for the contact, it can update the opportunity so your pipeline reflects the call. Action items also become tasks on a Greg project board.
Permissions Greg requests
These are the exact scopes requested during install, and why each one is needed. Greg does not request access to conversations, calendars, payments, or messaging in your CRM.
| Scope | Why it's needed |
|---|---|
| contacts.readonly | Find the CRM contact that matches a meeting attendee, so the note lands on the right record. |
| contacts.write | Write the meeting summary and action items onto that contact as a note. |
| opportunities.readonly | Look up the contact's opportunity and read your pipelines and stages. |
| opportunities.write | Update the opportunity after a call so the pipeline reflects the conversation. |
| locations.readonly | Read the accounts you chose during Marketplace install so Greg can attach to the right workspace. |
| oauth.readonly | Agency installs only: list the accounts the app was installed into. |
| oauth.write | Agency installs only: mint a per-account access token so each account is handled separately. |
What Greg writes into the CRM
- • A contact note — the meeting summary and action items, attached to the matching contact.
- • An opportunity update — where the contact has an opportunity, so the pipeline reflects what was discussed.
Greg does not delete CRM records, and does not modify contacts beyond adding notes.
Agencies and multiple accounts
Installing at the agency level lets one install cover many client accounts. Greg lists the accounts the install granted access to and obtains a separate access token per account, so each client's data stays scoped to that account. You choose which account a Greg workspace writes to from Settings → Integrations.
Troubleshooting
- The install finished but no CRM account shows in Greg
- Open Settings → Integrations and reconnect. For agency installs, confirm the account you expect was actually selected during install — access is granted only for the accounts you ticked.
- Notes aren't appearing on the contact
- Greg matches meeting attendees to CRM contacts by email address. If the attendee's email isn't on a contact record, there is nothing to attach the note to. Add the email to the contact and the next meeting will match.
- The notetaker didn't join a meeting
- Check that the event is on the connected calendar and has a Google Meet, Zoom, or Teams link on it. Meetings without a joinable link can't be attended. You can still upload a recording afterwards.
- The Greg tab in the CRM is blank
- Reload the tab once — the first load completes a handshake that registers your CRM domain, including custom domains like
crm.youragency.com. No setup is needed on our side. If it is still blank after a reload, your browser console will show a Content-Security-Policy “frame-ancestors” message; send us that and the domain your team logs into. - Connecting Google Calendar does nothing inside the panel
- Google refuses to load its sign-in screen inside an embedded frame, so Greg opens it in a separate window instead. If nothing appears, your browser blocked the popup — allow popups for the CRM domain and try again.
- The opportunity wasn't updated
- Opportunity updates require the contact to already have an opportunity in a pipeline Greg can see. If the contact has no opportunity, the note is still written to the contact record.
Disconnecting
You can disconnect the CRM connection at any time from Settings → Integrations in Greg, or uninstall the app from the Marketplace. Once disconnected, Greg stops reading from and writing to your CRM. Notes already written remain on your contacts — they are your records.
Still stuck?
Email hello@getgreg.io. Privacy details are on this website's privacy policy.