1. Choose whose key to use
A Fireflies API key belongs to the user it comes from, and reads what that user can see in Fireflies: the meetings they own and the meetings shared with them. A meeting that is private to its owner stays out of reach of every other user’s key. So use the key of a Fireflies admin who is invited to, or has access to, the meetings Neo should read, such as your client calls. An admin’s key also reads your team’s users and analytics. On the Enterprise plan, a Super Admin’s key reads every meeting of the team.2. Copy the API key
In Fireflies, open Integrations → Fireflies API and copy the API key. Keep it out of email and chat: anyone who has it can read the meetings it sees. Neo calls Fireflies athttps://api.fireflies.ai/graphql with the key as a Bearer token.
3. Add the key in Neo
1
Open Integrations
In the Neo Dashboard, open Integrations and find the Fireflies card, under Customer Success.
2
Save the key
Paste the API key and click Save settings. Neo checks it against Fireflies before saving, so a wrong or revoked key is rejected straight away.
4. Turn Fireflies on per agent
Open the agent, go to the Integrations section, and pick an access profile for the Fireflies block, or set each area yourself:
To save client context as memory, the agent also needs Agent Memories at Read / Write in its Neo API block, with approval on. See Fireflies API for the profiles.