Fireflies
Connect Fireflies to Ploy to see everyone on your Fireflies team, which of them are team admins, and which user groups each person belongs to. The integration reads only; it never changes anything in Fireflies.
This integration is in beta
The Fireflies integration is in beta. It was built from Fireflies' documented API and has not yet been run against a live Fireflies team, so some behaviour may differ from what is described here until it has.
The first step of setup is a consent checkbox. Ticking it lets Ploy send redacted error data to its own monitoring when a call to Fireflies fails. Redacted means secrets, tokens and personal details are removed before anything is stored. Ploy uses it only to fix problems with the integration. You need to tick it to continue.
What Ploy reads
Every user on your Fireflies team, with their email address and name.
Whether each person is a team admin. Ploy shows this as an Admin or Member entitlement on their Fireflies access.
Every user group on the team, and who belongs to it.
People removed from your Fireflies team lose their access in Ploy on the next scan. Fireflies has no suspended state for team members. Channels, meetings and sign-in activity are not scanned.
Ploy scans every six hours. Fireflies' Free plan allows 50 API requests a day, and each scan uses two.
What Ploy can change
Nothing. Fireflies' API cannot invite, remove or suspend team members, change who is an admin, or change user group membership, so these are managed in Fireflies itself.
Before you start
You need the API key of a Fireflies team admin:
Sign in to Fireflies as a team admin.
Open Integrations, then Fireflies API.
Copy the API key and keep it somewhere safe. Treat it like a password.
The key belongs to the person who created it, and Ploy acts as that person. Use an admin who will stay on the team: if they leave, the key stops working. User groups can only be read with an admin's key.
Connect Fireflies
In Ploy, open Integrations and choose Fireflies.
Tick the beta consent checkbox.
Paste the API key.
Select Test to check the key. Ploy reads your team's users to confirm it works.
Save the connection. The first scan starts straight away.
Connect one Fireflies team per Ploy organisation. Fireflies does not tell Ploy which team a key belongs to, so two teams connected to the same organisation would overwrite each other's users.
Troubleshooting
Fireflies rejected that API key: check the key was copied in full and that the person who created it is still on the team.
Fireflies refused to list your team: use an API key that belongs to a team admin.
Fireflies has rate limited this API key: the plan's daily request limit was reached. Wait a while and test again.