Mailboxes & agendas
Mailboxes & agendas
# Gmail and Google Calendar
# Synchronization with Skalin
To connect to your e-mail accounts and calendars, you first need to whitelist Skalin on your Google Workspace environment. This should be done by a Google Workspace administrator, and the process is fairly straightforward.
Once Skalin has been approved, go to https://app.skalin.io/#/integration/gmail (opens new window) to connect your Gmail inbox and Google calendar.
Click on the "Sign-in with Google" button:
Select the appropriate account:
Finally, click on authorize. That's it, you're connected!
By default, only your main calendar is synchronized. You can add your secondary calendars as required. Click "Save" to save your configuration.
All you have to do is wait a few hours for the initial synchronization to take place. Thereafter, your messages and appointments will be synchronized every hour.
# Whitelisting of Skalin within Google Workspace
It is possible that the administrator of your Google Workspace account has security rules that block authentication. In this case, your administrator will need to approve the Skalin application within Google Workspace.
In this case, go to the administration console https://admin.google.com/ (opens new window)
Then : Security > Access & Data Control > API commands > Application access control 
Then click on “MANAGE ACCESS FOR APPLICATIONS” then click on “Configure a new application” 
Fill in the following form:
- Application : Search for Skalin app thanks to its identifier: 1084505231477-a7f3mcoo4bqu6rvtrtj65ip5arcl4dmn.apps.googleusercontent.com Select Skalin line and continue.
- Application field : Select all your organieation users or a predefined unit.
- Google data access: Select "Trusted". Limited and Specific Google data authrizations are not sufficient for Skalin to work properly. Trusting Skalin app doesn't give it all permissions, only when users will connect their Google accounts will they grant permissions to some specific scopes, mainly reading and writing emails and reading the agenda.
- Summary
Check the configuration and finish.
Info
Granting access takes place in two steps. First, whitelisting Skalin in Google Workspace only allows the application to be available within your organization — it does not grant any access to user data. Actual authorization occurs when each user connects their Google account and explicitly approves Skalin’s requested permissions.
Once this authorization is completed, Skalin strictly limits its scope to emails and meetings that involve both a Skalin user and a contact recorded in Skalin. No other emails, events, or content are accessed or logged.
# Microsoft 365
Go to https://app.skalin.io/#/integration/microsoft (opens new window) to connect your MS365 box and your Microsoft calendar. Click on the "Connect me" button. Select the account you wish to synchronize, enter your credentials if applicable, then authorize Skalin to access your information. You're connected!
All you have to do is wait a few hours for the initial synchronization to take place. Thereafter, your messages and appointments will be synchronized every hour.
Similar example with Google:
# Slack
Slack integration will enable your team to receive alerts or notifications, either on a shared channel (public channels only), or live via the Skalin Bot.
To connect, go to https://app.skalin.io/#/integration/slack (opens new window) and click on "Connect me". Select the Slack account you want to connect (top right), check the requested permissions and click "Allow".
You will then be prompted to choose a default communication channel. Each time you set up a Slack alert or notification at a Playbook, you'll be able to use this default channel, or choose another channel, or send messages to specific users.
From now, you can use Slack for Alerts and Playbooks.
# 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
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
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.