Meeting notes
Bring the summary, action items, and transcript of a recorded meeting from your notetaker into the conversation with that person.
You already record calls with a notetaker such as Fireflies, Fathom, Otter, Granola, Read AI, tl;dv, or the notes that Zoom, Google Meet, and Microsoft Teams write. CommSync puts each meeting in the conversation with the person you met. Their email, their texts, and your meetings with them are then in one thread.
CommSync does not join or record your meetings. Your notetaker keeps doing that. CommSync receives what it wrote.
What you see
A meeting shows as a card in the conversation, at the time the meeting started:
- The title, the platform, the time, the length, and the notetaker.
- The people who were there.
- The summary and the action items.
- The transcript, folded by speaker. Open it in place to read all of it, or copy it.
- A link back to the recording in your notetaker.
The inbox row reads Meeting: and the title. A meeting does not add an unread count, send a notification, take an archived conversation out of the archive, or put the conversation in Waiting on you, because you were there. It is in search, and Ask can answer questions about it.
Where a meeting goes
CommSync picks the conversation from the people in the meeting:
- It drops your own addresses, your lines, and your teammates.
- It looks for your most recent conversation with one of the other people. A saved contact counts all of its email addresses and numbers, so a meeting can land in that person's text conversation too.
- When you have no conversation with any of them, it starts a new email conversation with the first outside person, on your email line.
To choose the conversation yourself, send contactEmail, contactPhone,
or threadId with the meeting.
Same meeting, one card
CommSync knows a meeting by the notetaker name and the notetaker's own id. When the same meeting comes again, CommSync updates its card and adds no second one. Many notetakers send the transcript first and the summary later, and both end up on one card.
Connect your notetaker
All three ways use the same CommSync sign-in: an API key, or OAuth for an AI app. A key that you limit to some lines reaches only conversations on those lines.
Most notetakers have a Zapier trigger such as "New meeting" or "Transcript ready". Make and n8n work the same way.
Create a key
In CommSync, open Settings → API Keys and create a key. Copy it.
Pick the trigger
In Zapier, pick your notetaker's trigger for a finished meeting.
Add the request
Add Webhooks by Zapier → Custom Request. Set the method to POST, the URL to
https://server.commsync.ai/api/meetings, and the header Authorization to Bearer csk_… with
your key.
Map the fields
Send JSON with the fields in the table below, mapped from the trigger. Use the notetaker's
meeting id as externalId.
Fields
| Field | Required | What it is |
|---|---|---|
source | Yes | The notetaker, for example fireflies, fathom, otter, zoom. Use custom for your own tool |
externalId | Yes | The notetaker's id of the meeting. The same source and externalId update one card |
title | Yes | The meeting title, up to 300 characters |
startedAt | Yes | When the meeting started, ISO 8601 |
endedAt | No | When it ended. CommSync counts the length from it |
durationSeconds | No | The length, when you have no end time |
meetingUrl | No | The join link. CommSync reads the platform from it: Zoom, Google Meet, Teams, Webex |
platform | No | ZOOM, GOOGLE_MEET, MICROSOFT_TEAMS, WEBEX, SLACK, PHONE, IN_PERSON, or OTHER |
recordingUrl | No | A link to the recording or the notes in your notetaker |
attendees | No | Up to 50 people: name, email, phone |
summary | No | Up to 20,000 characters |
actionItems | No | Up to 50 lines |
transcript | No | The transcript as plain text, up to 500,000 characters |
transcriptSegments | No | The transcript by speaker: speaker, text, startSeconds. Up to 10,000 turns and 500,000 characters in total. Send this or transcript |
contactEmail, contactPhone | No | Put the meeting in the conversation with this person |
threadId | No | Put the meeting in this conversation |
addActionItemsAsTodos | No | true also adds each action item as a to-do on your Home, tied to the conversation. Default false. Sending the same meeting again adds no duplicate to-dos |
Answers
| Status | When |
|---|---|
201 | A new card. The body has threadId, messageId, isNew, newThread, and match |
200 | The same meeting came again, and its card was updated |
400 | The payload is not valid. issues names each field |
401 | The key or the token is missing or not valid |
404 | threadId is not a conversation that your key can reach |
409 | The same meeting is already in a conversation that your key cannot reach. Ask a teammate who can see it, or use a key with more lines |
422 | No outside person has an email or a phone, or no conversation exists and you have no email line |
match says how CommSync chose the conversation: thread_id, contact,
or new_thread. todosCreated says how many to-dos the call added (0 unless
you sent addActionItemsAsTodos: true).
Privacy
CommSync stores the text your notetaker sends and the link to the recording. It does not download the recording. A meeting card is visible to every teammate who can see that conversation, the same as an email in it. CommSync AI does not reply to a meeting or make smart cards from it.