fireflies-data-handling
Handle Fireflies.ai transcript data: export formats, PII redaction, retention policies, and compliance. Use when exporting transcripts, implementing data redaction, configuring retention, or ensuring GDPR/CCPA compliance. Trigger with phrases like "fireflies data", "fireflies PII", "fireflies GDPR", "fireflies data retention", "fireflies privacy", "fireflies export".
What this skill does
# Fireflies.ai Data Handling
## Overview
Manage meeting transcript data: export in multiple formats (JSON, text, SRT), redact PII from transcripts and summaries, implement retention policies with automated cleanup, and handle GDPR/CCPA data subject requests.
## Prerequisites
- `FIREFLIES_API_KEY` configured
- Understanding of transcript data structure (sentences, summary, analytics)
- Storage for processed transcripts
## Instructions
### Step 1: Fetch Transcript Data
```typescript
const FIREFLIES_API = "https://api.fireflies.ai/graphql";
async function getFullTranscript(id: string) {
const res = await fetch(FIREFLIES_API, {
method: "POST",
headers: {
"Content-Type": "application/json",
Authorization: `Bearer ${process.env.FIREFLIES_API_KEY}`,
},
body: JSON.stringify({
query: `
query($id: String!) {
transcript(id: $id) {
id title date duration
organizer_email
speakers { id name }
sentences { speaker_name text start_time end_time }
summary { overview action_items keywords short_summary }
meeting_attendees { displayName email }
}
}
`,
variables: { id },
}),
});
const json = await res.json();
if (json.errors) throw new Error(json.errors[0].message);
return json.data.transcript;
}
```
### Step 2: Export in Multiple Formats
```typescript
type ExportFormat = "json" | "text" | "srt" | "csv";
function exportTranscript(transcript: any, format: ExportFormat): string {
switch (format) {
case "json":
return JSON.stringify(transcript, null, 2);
case "text":
const lines = [
`# ${transcript.title}`,
`Date: ${transcript.date} | Duration: ${transcript.duration}min`,
`Speakers: ${transcript.speakers.map((s: any) => s.name).join(", ")}`,
"",
"## Summary",
transcript.summary?.overview || "(none)",
"",
"## Action Items",
...(transcript.summary?.action_items || []).map((a: string) => `- ${a}`),
"",
"## Transcript",
...transcript.sentences.map((s: any) =>
`[${fmtTime(s.start_time)}] ${s.speaker_name}: ${s.text}`
),
];
return lines.join("\n");
case "srt":
return transcript.sentences.map((s: any, i: number) =>
[
i + 1,
`${fmtSrt(s.start_time)} --> ${fmtSrt(s.end_time)}`,
`${s.speaker_name}: ${s.text}`,
"",
].join("\n")
).join("\n");
case "csv":
const header = "start_time,end_time,speaker,text";
const rows = transcript.sentences.map((s: any) =>
`${s.start_time},${s.end_time},"${s.speaker_name}","${s.text.replace(/"/g, '""')}"`
);
return [header, ...rows].join("\n");
}
}
function fmtTime(sec: number): string {
const m = Math.floor(sec / 60);
const s = Math.floor(sec % 60);
return `${String(m).padStart(2, "0")}:${String(s).padStart(2, "0")}`;
}
function fmtSrt(sec: number): string {
const h = Math.floor(sec / 3600);
const m = Math.floor((sec % 3600) / 60);
const s = Math.floor(sec % 60);
const ms = Math.floor((sec % 1) * 1000);
return `${String(h).padStart(2, "0")}:${String(m).padStart(2, "0")}:${String(s).padStart(2, "0")},${String(ms).padStart(3, "0")}`;
}
```
### Step 3: PII Redaction
```typescript
const PII_PATTERNS = [
{ regex: /\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}\b/g, tag: "[EMAIL]" },
{ regex: /\b\d{3}[-.]?\d{3}[-.]?\d{4}\b/g, tag: "[PHONE]" },
{ regex: /\b\d{3}-\d{2}-\d{4}\b/g, tag: "[SSN]" },
{ regex: /\b\d{4}[\s-]?\d{4}[\s-]?\d{4}[\s-]?\d{4}\b/g, tag: "[CARD]" },
{ regex: /\b\d{1,5}\s+\w+\s+(Street|St|Avenue|Ave|Road|Rd|Drive|Dr|Lane|Ln)\b/gi, tag: "[ADDRESS]" },
];
function redactText(text: string): string {
let result = text;
for (const { regex, tag } of PII_PATTERNS) {
result = result.replace(regex, tag);
}
return result;
}
function redactTranscript(transcript: any): any {
return {
...transcript,
// Redact organizer email
organizer_email: redactText(transcript.organizer_email || ""),
// Redact sentences
sentences: transcript.sentences?.map((s: any) => ({
...s,
text: redactText(s.text),
speaker_name: s.speaker_name, // Keep speaker names for context
})),
// Redact summary fields too
summary: transcript.summary ? {
...transcript.summary,
overview: redactText(transcript.summary.overview || ""),
action_items: transcript.summary.action_items?.map(redactText),
short_summary: redactText(transcript.summary.short_summary || ""),
} : null,
// Redact attendee info
meeting_attendees: transcript.meeting_attendees?.map((a: any) => ({
displayName: a.displayName,
email: redactText(a.email || ""),
})),
};
}
```
### Step 4: Retention Policy with Automated Cleanup
```typescript
interface RetentionPolicy {
fullTranscriptDays: number; // Keep full sentences
summaryDays: number; // Keep summary after transcript deleted
deleteAfterDays: number; // Delete everything
}
const DEFAULT_POLICY: RetentionPolicy = {
fullTranscriptDays: 90,
summaryDays: 365,
deleteAfterDays: 730,
};
async function applyRetentionPolicy(policy = DEFAULT_POLICY) {
const data = await getTranscriptList(200);
const now = Date.now();
const results = { kept: 0, archived: 0, deleted: 0 };
for (const t of data.transcripts) {
const ageDays = (now - new Date(t.date).getTime()) / 86400000;
if (ageDays > policy.deleteAfterDays) {
// Delete from Fireflies
await deleteTranscript(t.id);
results.deleted++;
} else if (ageDays > policy.fullTranscriptDays) {
// Archive: keep summary only in your DB
await archiveToSummaryOnly(t.id);
results.archived++;
} else {
results.kept++;
}
}
console.log(`Retention applied: ${results.kept} kept, ${results.archived} archived, ${results.deleted} deleted`);
return results;
}
async function deleteTranscript(id: string) {
// Rate limit: 10 deletes per minute
await fetch(FIREFLIES_API, {
method: "POST",
headers: {
"Content-Type": "application/json",
Authorization: `Bearer ${process.env.FIREFLIES_API_KEY}`,
},
body: JSON.stringify({
query: `mutation($id: String!) { deleteTranscript(transcript_id: $id) }`,
variables: { id },
}),
});
// Respect rate limit
await new Promise(r => setTimeout(r, 6500));
}
```
### Step 5: GDPR Data Subject Request
```typescript
// Handle "right to be forgotten" requests
async function handleDataSubjectDeletion(email: string) {
// Find all transcripts where this person participated
const data = await fetch(FIREFLIES_API, {
method: "POST",
headers: {
"Content-Type": "application/json",
Authorization: `Bearer ${process.env.FIREFLIES_API_KEY}`,
},
body: JSON.stringify({
query: `query($participants: [String]) {
transcripts(participants: $participants, limit: 100) {
id title date participants
}
}`,
variables: { participants: [email] },
}),
}).then(r => r.json());
const affected = data.data.transcripts;
console.log(`Found ${affected.length} transcripts with ${email}`);
// Option 1: Delete transcripts entirely
// Option 2: Redact the person's contributions
// Choose based on your legal requirements
return {
email,
affectedTranscripts: affected.length,
transcriptIds: affected.map((t: any) => t.id),
};
}
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Missing sentences | Transcript still processing | Check before export |
| PII in action items | Redaction only on sentences | Redact summary fields too (Step 3 does this) |
| Delete rate limit | 10 deletes/min | Add 6.5s delay between deletes |
| Large transcript OOM | 2+ hour meeting | Stream or paginate sentences |
## Output
- Multi-fRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.