Send notes from a meeting-notes tool such as Granola to Plum, and each note is filed under the account whose people were in the meeting.
Setting it up: owners and admins
Plum gives your workspace a web address and a secret. Any tool that can send a web request, such as Granola by way of Zapier, posts each note there. Plum matches the attendees' email addresses to your accounts and adds the note to that account's activity.
Set it up
- Go to Integrations and choose Meeting notes. This opens Notes and email.
- Under Connection, choose Create a secret.
- Copy the secret straight away. It is shown once and can't be shown again.
- In your automation, send each note as JSON in a POST to the address shown, with the header Authorization: Bearer followed by your secret.
- Map your tool's fields onto Plum's, using the table on the page, and send a test note.
The page also has step-by-step instructions for Granola with Zapier. Connection shows when the secret was created and when it was last used.
The fields
- title
- Required. The meeting's title.
- attendees
- Who took part, with email addresses. This is how the note finds its account.
- creator_email
- Your own address, so your colleagues aren't mistaken for the customer.
- summary
- The notes or summary, up to 50,000 characters.
- occurred_at
- When the meeting was. If it is missing, unreadable or more than a day ahead, Plum uses the time the note arrived.
- link
- A link back to the note. Kept only if it is a plain https address.
- id
- The note's own id, so the same note sent twice is stored once.
- transcript
- The full transcript. Kept only if your workspace has turned transcripts on.
How a note is filed
- People on your side are set aside: the creator, others at the creator's company domain (unless it's a public mail provider), and anyone at a domain your workspace has verified.
- Each other person points to an account: their contact record first, otherwise the account with their email domain.
- The account with the most people wins. If none matches, or two tie, the note goes to the Inbox.
- If that account has exactly one open deal, the note is linked to it too.
- People at the account who aren't contacts yet are added as contacts.
Matching is by email address, never by name. Addresses at public mail providers, such as Gmail, never match an account by domain.
Transcripts
Summaries are always kept. Full transcripts are kept only if an owner or admin ticks Keep full transcripts under Transcripts and saves; it's off by default. A transcript is available to everyone in the workspace who can open the account. Turning the setting off stops new transcripts being kept, but doesn't delete ones already stored.
Replacing the secret
Choose Replace the secret if it may have leaked, or if someone who knew it has left. The old secret stops working at once, so update your automation with the new one. The workspace's email capture address changes too.
Plum accepts up to 120 notes an hour for a workspace. A request without your workspace's secret is refused, and so are notes for a workspace that is suspended or cancelled.