Documentation Index
Fetch the complete documentation index at: https://help.statisfy.com/llms.txt
Use this file to discover all available pages before exploring further.
Connect Fireflies with Statisfy
The Fireflies integration pulls meeting transcripts and AI-generated summaries from your Fireflies workspace into Statisfy. Meetings are matched to the right customer account by attendees and appear alongside the rest of the activity timeline. Prerequisites:- Admin access to both Fireflies and Statisfy
- A Fireflies API key
- A connected CRM (Salesforce or HubSpot) — non-CRM integrations are gated until at least one CRM sync has completed
What Gets Synced
| Data Type | Description |
|---|---|
| Meeting Transcripts | Full speaker-tagged transcripts pulled from Fireflies |
| Summaries | AI-generated overview, action items, keywords, topics discussed, and chapters |
| Attendees | Meeting participants (internal and external) with email addresses |
| Meeting Metadata | Title, date, duration, organizer, host, meeting link, and calendar type |
Generate a Fireflies API Key
- Sign in to Fireflies as a workspace admin.
- Open Integrations → API in your Fireflies workspace settings and create a new API key. Refer to Fireflies’ developer documentation for the latest steps.
- Copy the key — you’ll provide it to Statisfy in the next step.
Steps to Connect with Statisfy
- Log in to Statisfy.
- Navigate to Integrations → Fireflies → Connect and paste your API key. Credentials are stored encrypted in Google Cloud Secret Manager.
- Once connected, the bootstrap job runs a one-time historical backfill. Transcripts and summaries flow into Statisfy.
- The periodic sync runs on a recurring schedule with a short lookback window so updates to existing meetings are picked up alongside new ones.
- Find synced meetings on each Account under AI Timeline → Source: Fireflies, or in the global Activities view filtered by source.
Sync Behavior
Time-bounded pulls:- Transcripts are fetched in batches by date range using the Fireflies GraphQL API.
- Each periodic run looks at the last couple of days so edits to recent meetings are caught.
- Statisfy classifies internal vs. external attendees by email domain.
- Speaker labels in the transcript are passed through as-is from Fireflies.
- If Fireflies returns HTTP 401, the credential is automatically marked invalid in Statisfy — reconnect with a fresh key.
- GraphQL errors are logged and the affected batch is skipped; the next run will retry.
Troubleshooting
Authentication failed
Authentication failed
- Verify the API key has not been rotated or revoked in Fireflies.
- If Statisfy detects an HTTP 401, the credential is automatically marked invalid — reconnect with a fresh key.
Meetings not appearing in Statisfy
Meetings not appearing in Statisfy
- Ensure your CRM integration (Salesforce or HubSpot) has completed at least one successful sync. Until then, Fireflies periodic jobs are skipped.
- Confirm the meeting’s external attendees match an existing account by email domain or CRM linkage.
- Very recent meetings may not yet have a finalized transcript in Fireflies; they’ll appear on a later run.
Duplicate meetings on the timeline
Duplicate meetings on the timeline
- Statisfy deduplicates by transcript ID within a run. If you also have another meeting source (e.g., Gong, Zoom) connected, the same meeting could surface from multiple sources. Filter by Source in the Activities view to see where each entry came from.