Meetings & conversations integration
Meetings & conversations integration
# Importing your meetings into Skalin
The connectors in this category bring the summaries and transcripts of your recorded meetings into Skalin, so they are centralized on the customer record, alongside emails, calls and meetings. The connection differs from one tool to another (see each connector below), but the import configuration is the same.
# What to do with the summary
For each recorded meeting, you choose how the summary is added to Skalin:
- Create a note: each recording becomes a note on the customer record, addressed to the external participants.
- Replace the meeting description: the summary is added to the description of the corresponding meeting already in Skalin, instead of creating a separate note.
Which one to choose?
- Creating a note makes filtering easier: you can find all your meeting summaries directly by filtering on notes.
- Updating the meeting avoids ending up with two separate interactions (the meeting and the note) that refer to the same meeting.
You can customize the note title: the field accepts the variable, which is replaced with the meeting title (for example Summary - ).
# Imported content
Two options complete the content brought into Skalin:
- Include action items: adds the action items and follow-ups identified during the meeting to the summary.
- Include the link to the recording: adds a direct link to the meeting recording.
# Filters
You can restrict the meetings that are imported using filters, for example: the team, the member who recorded the meeting, or the meeting type. Leave a filter empty to skip it.
AI assistant
In all cases, the imported summary is taken into account by Skalin's AI assistant: you can ask it questions about the content of your meetings.
# Fathom
Fathom (opens new window) records your meetings and writes an AI summary of them. The Skalin integration pulls that summary and attaches it to the right customer automatically.
# Create the API key
Go to developers.fathom.ai (opens new window), API Keys section, and create a key.
Beware: a key is personal. It only grants access to the recordings of the user who created it and those shared with their Fathom team. Each CSM therefore has to connect their own key from their Skalin account.
# Connect Fathom to Skalin
In Settings → Integrations → Fathom, click Connect and paste the API key. Skalin checks the key straight away.
# Choose what lands in Skalin
The summary has one destination, picked under What to do with the summary:
- Create a note — every Fathom recording becomes a note on the customer, addressed to the external attendees of the meeting. This is the default.
- Replace the meeting description — the summary is attached to the meeting already imported from your calendar (Google or Microsoft) and replaces its description. When no calendar meeting matches, a meeting is created.
The two are exclusive: combining them would make the same recording show up twice in the activity feed.
Careful with the second one: the description is rewritten on every synchronisation, so a description typed by hand in Skalin will be overwritten. The calendar synchronisation (Google or Microsoft 365) also has to be active, as it is what creates the meeting Fathom then completes.
# Imported content
- Fathom's AI summary, converted to formatted text.
- The action items captured during the meeting (optional).
- A link to the Fathom recording (optional).
# Filters
Fathom teams, Recorded by, Meeting type: leave empty to pull everything.
In every case, a recording is only imported when at least one attendee is a contact known to Skalin. That contact is what determines the customer the note or the meeting is attached to. Internal meetings, with no attendee outside your company, therefore never come through.
# Good to know
- Synchronisation is periodic: allow up to an hour between Fathom finishing the recording and it showing up in Skalin.
- A recording without a summary (Fathom still processing) is skipped and picked up on the next synchronisation.
# Fireflies
Fireflies (opens new window) transcribes your meetings and writes an AI summary of them. The Skalin integration pulls that summary and attaches it to the right customer automatically.
# Getting the API key
Go to app.fireflies.ai (opens new window), section Integrations → Fireflies API, and copy the key.
Careful: a key is personal. It only grants access to the meetings of the user who created it and those shared with their Fireflies team. Every CSM therefore has to connect their own key from their Skalin account.
Mind the quota too: on the Free and Pro plans, Fireflies caps the API at 50 and 500 calls per day — a quota shared with your other connected tools. Business and Enterprise plans move to 60 calls per minute.
# Connecting Fireflies to Skalin
In Settings → Integrations → Fireflies, click Connect and paste the API key. Skalin checks the key straight away.
# Choosing what lands in Skalin
The summary has one destination, picked under What to do with the summary:
- Create a note — every transcribed meeting becomes a note on the customer, addressed to the external attendees. This is the default.
- Replace the meeting description — the summary is attached to the meeting already imported from your calendar (Google or Microsoft) and replaces its description. When no calendar meeting matches, a meeting is created.
The two are exclusive: combining them would show the same meeting twice in the activity feed.
Careful with the second one: the description is rewritten on every synchronisation, so a description typed by hand in Skalin will be overwritten. The calendar synchronisation (Google or Microsoft 365) also has to be active, as it is what creates the meeting Fireflies then completes.
# Imported content
- The Fireflies AI summary, converted to formatted text. Fireflies produces several renderings of the same summary (detailed, notes, bullet lists, one sentence): Summary format picks the one to import. When it is empty for a given meeting, Skalin falls back on another rendering rather than skipping the meeting.
- The custom sections you added to your summary template from the Fireflies dashboard (optional).
- The action items captured during the meeting (optional).
- A link to the Fireflies transcript (optional).
# Filters
Organised by, Fireflies channel: leave empty to import everything.
In every case, a meeting is only imported when at least one attendee is a contact Skalin knows. That contact is what determines the customer the note or the meeting is attached to. Internal meetings, with no attendee outside your company, therefore never land.
# Good to know
- The synchronisation is periodic, count up to an hour between Fireflies finishing the transcript and it reaching Skalin.
- A meeting whose summary is still being generated is skipped and picked up on the next run: Skalin systematically re-reads the last 24 hours for that reason.
- A meeting still in progress is never imported.
# Noota
The connection to Noota is set up using an API key.
Business account required
Creating an API key requires a Noota business account.
Each user must create their own API key, unless the administrator has access to all of the team's conversations, in which case a single key is enough.
Noota (opens new window) records your meetings and writes an AI report of them. The Skalin integration pulls that report and attaches it to the right customer automatically.
# Getting the API key
The key is found in your Noota account settings, API section.
Careful: a key is personal. It only grants access to the recordings of the user who created it. Every CSM therefore has to connect their own key from their Skalin account.
# What lands in Skalin
Every Noota recording becomes a note on the customer, addressed to the external attendees of the meeting.
Unlike the Fathom and Fireflies integrations, the report cannot replace the description of a calendar meeting. That is a limitation of the Noota API rather than a choice: to pair a recording with the matching meeting, Skalin needs the scheduled time of the meeting, and Noota only exposes the moment recording started — seconds to minutes later. A meeting built on that would never pair with the calendar one and would show up twice in the activity feed.
# Imported content
- The Noota AI report, with the formatting it has in Noota.
- A link to the original meeting (video call) when Noota knows it (optional).
# Filters
Recorded by: the address of the Noota account owning the recordings. Leave empty to import everything.
In every case, a recording is only imported when at least one attendee is a contact Skalin knows. That contact is what determines the customer the note is attached to. Internal meetings, with no attendee outside your company, therefore never land.
# Good to know
- The synchronisation is periodic, count up to an hour between Noota finishing the recording and it reaching Skalin.
- Only recordings whose transcription is complete are picked up. One still being processed is skipped and taken on the next run: Skalin systematically re-reads the last 24 hours for that reason.
- The note carries the attendees' addresses, not their names: the Noota API only returns names alongside the full verbatim transcript, which would be disproportionate to download for that.
# tl;dv
To connect tl;dv, go to the tl;dv integration page in Skalin and fill in the information requested on screen.
Paid plan required
API access is not available on the tl;dv free plan. You must have one of tl;dv's three paid accounts to connect the integration.
tl;dv (opens new window) records your meetings and writes AI notes of them. The Skalin integration pulls those notes and attaches them to the right customer automatically.
# Creating the API key
In tl;dv, go to Personal settings → API keys and create a key.
A Business or Enterprise account is required: free and Pro accounts have no API access.
Careful: a key is personal. It only grants access to the meetings the account that created it can reach. Every CSM therefore has to connect their own key from their Skalin account.
# Connecting tl;dv to Skalin
In Settings → Integrations → tl;dv, click Connect and paste the API key. Skalin checks the key straight away.
# Choosing what lands in Skalin
The notes have one destination, picked under What to do with the notes:
- Create a note — every recorded meeting becomes a note on the customer, addressed to the external attendees. This is the default.
- Replace the meeting description — the notes are attached to the meeting already imported from your calendar (Google or Microsoft) and replace its description. When no calendar meeting matches, a meeting is created.
The two are exclusive: combining them would show the same meeting twice in the activity feed.
Careful with the second one: the description is rewritten on every synchronisation, so a description typed by hand in Skalin will be overwritten. The calendar synchronisation (Google or Microsoft 365) also has to be active, as it is what creates the meeting tl;dv then completes.
# Imported content
- The tl;dv AI notes. They come in two shapes — a written summary and the meeting chapters — and Notes format picks the one to import. When it is empty for a given meeting, Skalin falls back on the other rather than skipping the meeting.
- A link to the tl;dv recording (optional).
# Filters
Unlike the other notetakers, tl;dv can rule out internal meetings itself: it compares the organizer's email domain with the attendees' and only returns meetings with at least one attendee on another domain. Skalin relies on that filter, so internal meetings are never downloaded at all.
My meetings only narrows it further to the meetings the key owner attended. Leave it off to import every meeting the key can reach.
In every case, a meeting is only imported when at least one attendee is a contact Skalin knows. That contact is what determines the customer the note or the meeting is attached to.
# Good to know
- The synchronisation is periodic, count up to an hour between the meeting ending and the notes reaching Skalin.
- The notes are written after the meeting: Skalin systematically re-reads the last 24 hours so a meeting summarised late is not missed.
- A meeting whose notes have not been generated yet is skipped and picked up on the next run.