Zentrik + Fireflies

An owner or admin connects Fireflies for the workspace. The connection supplies secure access to the meetings available to that Fireflies account; each saved import separately defines its meeting boundary, product context, and run policy.

Imported transcripts keep a link to the source meeting.

Choose the Fireflies account carefully. Zentrik can access only the meetings available to that account.

Before connecting:

1. Confirm the account can see the meetings your product team needs.
2. Confirm your team may bring those conversations into Zentrik.
3. Decide whether each saved import should use all accessible meetings or selected channels.

If the connected account cannot see a transcript in Fireflies, Zentrik cannot import it. Meeting privacy and channel visibility are separate in Fireflies: adding a meeting to a public channel does not make the transcript available to every teammate or API key.

Use a meeting privacy setting that includes teammates, such as Only Participants & Teammates or Only Teammates, when the connected API-key owner belongs to the same Fireflies workspace. Avoid Only Participants unless that account participated in the meeting.

Create the integration in Settings → Integrations → Fireflies and paste a Fireflies API key that has access to the transcripts your product team should import.

Open Discovery, click New, choose Bring in data, and select Fireflies. Search the meetings allowed by the connection’s Channel access setting, preview the relevant transcripts, and choose what to import.

Live arrival brings each meeting into Discovery as soon as Fireflies finishes its transcript, instead of waiting for the next scheduled run. Any schedule on the import stays on as the catch-up sweep.

An owner or admin turns it on from Settings → Integrations → Fireflies:

1. Turn on Live arrival. Zentrik shows a webhook URL and a signing secret.
2. In Fireflies, open Settings → Developer settings, paste both values, and save.
3. Every saved import on the connection now arrives live. Switch off Arrive live in a saved import's run policy to keep that one on schedule only.

Each meeting is checked exactly as a scheduled run would check it: the same channel scope, product routing, and attendee policy. A meeting outside the import's channels, or one the connected account cannot see, is skipped and never imported. Live imports appear in the run history as Arrived live.

Fireflies signs every delivery with the secret. If it stops matching the one in Zentrik, the connection page reports rejected deliveries; paste the current secret again, or create a new one from the same page.

• All accessible meetings: the saved import checks every completed meeting allowed by Channel access and visible to the connected account within its rolling lookback.
• Selected channels: the saved import checks only the chosen channels and can route each channel to a product.
• The connection owns credentials and Channel access. Each saved import separately owns its channel selection, product routing, schedule, and run history.
• One-time review remains available for selecting individual meetings without changing a saved import.
• A meeting must also be visible to the connected Fireflies account. A public channel does not override the meeting's own privacy setting.
• Saved imports can set a Recent lookback between 1 and 30 days; new definitions default to 30 days. Each run rechecks meetings whose meeting date falls within that rolling window, which can catch an older meeting after it is moved into a selected channel.
• The lookback uses the meeting date because Fireflies does not provide the date when a meeting was added to a channel. A meeting older than the configured lookback is not discovered automatically; use a one-time import with a wider date range.
• Wider windows require more Fireflies API work. If a run reports that its safe transcript limit was exceeded, reduce the lookback or narrow the selected channels.
• Fireflies workspace users and same-company attendees are treated as internal. A Fireflies user profile by itself does not make someone internal. Without a reliable workspace boundary, Zentrik can reuse one exact existing Person but does not create one.
• When attendee organization is enabled, reliably external attendees are matched or created as People. Account creation remains a separate opt-in; ambiguous matches stay unassigned instead of guessing. Generated insights inherit the Signal's Account links.