fireflies-rate-limits
Guidance on managing Fireflies.ai API rate limits with exponential backoff and request queuing.
Install
mkdir -p .claude/skills/fireflies-rate-limits && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5450" && unzip -o skill.zip -d .claude/skills/fireflies-rate-limits && rm skill.zipInstalls to .claude/skills/fireflies-rate-limits
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Implement Fireflies.ai rate limiting, backoff, and request queuing.Key capabilities
- →Detect rate limit errors in API responses
- →Queue batch operations to respect rate limits
- →Track daily API request budgets
- →Handle specific operation-level throttling
How it works
The skill manages API throughput by detecting 429 errors, applying exponential backoff with jitter for retries, and using a request queue to ensure operations stay within plan-specific limits.
Inputs & outputs
When to use fireflies-rate-limits
- →Implementing exponential backoff for API calls
- →Handling 'too_many_requests' error codes
- →Optimizing concurrent request throughput
- →Adding request queuing to avoid rate hitting
About this skill
Fireflies.ai Rate Limits
Overview
Handle Fireflies.ai GraphQL API rate limits with exponential backoff and request queuing. Fireflies enforces per-plan limits and per-operation limits.
Rate Limit Reference
Per-Plan Limits
| Plan | Limit | Scope |
|---|---|---|
| Free | 50 requests/day | Per API key |
| Pro | 50 requests/day | Per API key |
| Business | 60 requests/min | Per API key |
| Enterprise | 60 requests/min | Per API key |
Per-Operation Limits
| Operation | Limit | Error Code |
|---|---|---|
addToLiveMeeting | 3 per 20 minutes | too_many_requests |
shareMeeting | 10 per hour (up to 50 emails each) | too_many_requests |
deleteTranscript | 10 per minute | too_many_requests |
uploadAudio | Varies by plan | too_many_requests |
Instructions
Step 1: Detect Rate Limits in Responses
interface FirefliesError {
message: string;
code: string;
extensions?: { status: number };
}
function isRateLimited(response: any): boolean {
return response.errors?.some(
(e: FirefliesError) =>
e.code === "too_many_requests" ||
e.extensions?.status === 429
);
}
Step 2: Exponential Backoff with Jitter
async function firefliesQueryWithRetry<T>(
query: string,
variables?: Record<string, any>,
maxRetries = 5
): Promise<T> {
const FIREFLIES_API = "https://api.fireflies.ai/graphql";
for (let attempt = 0; attempt <= maxRetries; attempt++) {
const res = await fetch(FIREFLIES_API, {
method: "POST",
headers: {
"Content-Type": "application/json",
Authorization: `Bearer ${process.env.FIREFLIES_API_KEY}`,
},
body: JSON.stringify({ query, variables }),
});
const json = await res.json();
if (!isRateLimited(json)) {
if (json.errors) throw new Error(json.errors[0].message);
return json.data;
}
if (attempt === maxRetries) {
throw new Error(`Rate limited after ${maxRetries} retries`);
}
// Exponential backoff: 1s, 2s, 4s, 8s, 16s + jitter
const baseDelay = 1000 * Math.pow(2, attempt);
const jitter = Math.random() * 500;
const delay = Math.min(baseDelay + jitter, 32000);
console.log(`Rate limited. Retry ${attempt + 1}/${maxRetries} in ${delay.toFixed(0)}ms`);
await new Promise(r => setTimeout(r, delay));
}
throw new Error("Unreachable");
}
Step 3: Request Queue for Batch Operations
import PQueue from "p-queue";
// Business plan: 60 req/min = 1 req/sec safe rate
const firefliesQueue = new PQueue({
concurrency: 1,
interval: 1100,
intervalCap: 1,
});
async function queuedQuery<T>(query: string, variables?: Record<string, any>): Promise<T> {
return firefliesQueue.add(() => firefliesQueryWithRetry<T>(query, variables));
}
// Batch fetch transcripts without hitting rate limits
async function batchFetchTranscripts(ids: string[]) {
const results = [];
for (const id of ids) {
const data = await queuedQuery(`
query GetTranscript($id: String!) {
transcript(id: $id) {
id title date duration
summary { overview action_items }
}
}
`, { id });
results.push(data);
}
return results;
}
Step 4: Free/Pro Plan Daily Budget Tracker
class DailyBudgetTracker {
private count = 0;
private resetDate = new Date().toDateString();
private readonly dailyLimit: number;
constructor(plan: "free" | "pro" | "business") {
this.dailyLimit = plan === "business" ? Infinity : 50;
}
canRequest(): boolean {
this.resetIfNewDay();
return this.count < this.dailyLimit;
}
record(): void {
this.resetIfNewDay();
this.count++;
}
remaining(): number {
this.resetIfNewDay();
return Math.max(0, this.dailyLimit - this.count);
}
private resetIfNewDay(): void {
const today = new Date().toDateString();
if (today !== this.resetDate) {
this.count = 0;
this.resetDate = today;
}
}
}
const budget = new DailyBudgetTracker("pro");
if (!budget.canRequest()) {
console.log("Daily API limit reached. Try again tomorrow.");
}
Error Handling
| Scenario | Detection | Action |
|---|---|---|
| 429 response | code: "too_many_requests" | Exponential backoff |
| Daily limit hit (Free/Pro) | Track request count | Wait until next day |
addToLiveMeeting throttle | 3 per 20 min | Queue with 7-min spacing |
| Burst of webhook events | Many transcripts at once | Queue transcript fetches |
Output
- Rate-limit-aware GraphQL client with automatic retry
- Request queue preventing burst-induced throttling
- Daily budget tracker for Free/Pro plans
Resources
Next Steps
For security configuration, see fireflies-security-basics.
When not to use it
- →Applications that can tolerate frequent 429 errors
- →Systems where request latency is not a concern
Prerequisites
Limitations
- →Business/Enterprise plans have different limits than Free/Pro
- →Daily limits reset based on the calendar day
How it compares
It replaces naive request loops with a reliable queuing and retry mechanism that prevents hitting API rate limits.
Compared to similar skills
fireflies-rate-limits side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fireflies-rate-limits (this skill) | 1 | 25d | Caution | Intermediate |
| deepgram-performance-tuning | 3 | 25d | Review | Intermediate |
| graphql | 6 | 6mo | No flags | Advanced |
| guidewire-sdk-patterns | 2 | 25d | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
deepgram-performance-tuning
jeremylongshore
Optimize Deepgram API performance for faster transcription and lower latency. Use when improving transcription speed, reducing latency, or optimizing audio processing pipelines. Trigger with phrases like "deepgram performance", "speed up deepgram", "optimize transcription", "deepgram latency", "deepgram faster".
graphql
davila7
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
guidewire-sdk-patterns
jeremylongshore
Master Guidewire SDK patterns including Digital SDK, REST API Client, and Gosu best practices. Use when implementing integrations, building frontends with Jutro, or writing server-side Gosu code. Trigger with phrases like "guidewire sdk", "digital sdk", "jutro sdk", "guidewire patterns", "gosu best practices", "rest api client".
groq-performance-tuning
jeremylongshore
Optimize Groq API performance with caching, batching, and connection pooling. Use when experiencing slow API responses, implementing caching strategies, or optimizing request throughput for Groq integrations. Trigger with phrases like "groq performance", "optimize groq", "groq latency", "groq caching", "groq slow", "groq batch".
openrouter-streaming-setup
jeremylongshore
Implement streaming responses with OpenRouter. Use when building real-time chat interfaces or reducing time-to-first-token. Trigger with phrases like 'openrouter streaming', 'openrouter sse', 'stream response', 'real-time openrouter'.
perplexity-multi-env-setup
jeremylongshore
Configure Perplexity across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Perplexity configurations. Trigger with phrases like "perplexity environments", "perplexity staging", "perplexity dev prod", "perplexity environment setup", "perplexity config by env".