Skip to main content
skill CX Codex

fireflies-webhooks-events — Claude Code skill: Fireflies webhooks V2

fireflies-webhooks-events walks an agent through building a Fireflies Webhooks V2 receiver: raw-body HMAC check, event allowlisting, dedupe, and a 2xx reply fast enough for the 10-second window.

MIT 1 installs ★ 2,935 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jeremylongshore/tons-of-skills-marketplace --skill fireflies-webhooks-events -a claude-code
Open on GitHub

What fireflies-webhooks-events does

The skill covers the receiving side of Fireflies Webhooks V2: what to check before the payload becomes JSON, how to keep unknown events out of your handler, and how to avoid running the same side effect twice when a delivery repeats. It lays out seven steps, starting from subscribing to approved event types on an HTTPS endpoint and verifying X-Hub-Signature as sha256=<hex HMAC> over the raw bytes.

Verification runs on raw bytes, so parsing first breaks the check. Documented events are meeting.transcribed and meeting.summarized; the payload carries event, timestamp, meeting_id and an optional client_reference_id. Fireflies expects a 2xx within 10 seconds, so the skill advises acknowledging first and pulling data afterwards, out of band.

Credentials get their own section: FIREFLIES_API_KEY comes from a secret manager and travels only in an Authorization: Bearer header to https://api.fireflies.ai/graphql. The webhook signing secret is a separate credential and does not double as the API key. Live Fireflies calls need network access. Anything that widens scope, such as subscribing to team-wide events or fetching transcript content after an event, stops at an approval gate.

What it helps with

  • Verify X-Hub-Signature against the raw body before parsing
  • Quarantine unknown event types instead of guessing a schema
  • Keep the handler idempotent when a delivery repeats
  • Handle meeting.summarized arriving before meeting.transcribed
  • Return 2xx inside the 10-second window and move work to the background

Example prompts for the agent

  • Review the Fireflies webhook v2 consumer in apps/webhooks; start with the signature check and dedupe.
  • Verify Fireflies signature handling and point out where we parse JSON before the HMAC check.
  • Add a meeting.summarized handler with idempotency keyed on meeting_id.

How to install fireflies-webhooks-events

1Skills CLI (Vercel)

npx skills add jeremylongshore/tons-of-skills-marketplace --skill fireflies-webhooks-events -a claude-code

2Manually: put the files in place

~/.claude/skills/fireflies-webhooks-events/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/fireflies-webhooks-events/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about fireflies-webhooks-events

How do I install fireflies-webhooks-events in Claude Code?

Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill fireflies-webhooks-events -a claude-code. The skill lands at ~/.claude/skills/fireflies-webhooks-events/SKILL.md.

What does fireflies-webhooks-events do?

It guides an agent through a Fireflies Webhooks V2 receiver: HMAC over raw bytes, an allowlist of event types, dedupe, tolerance for out-of-order delivery, and a quick 2xx.

Does the skill need a Fireflies API key?

Live calls take FIREFLIES_API_KEY from a secret manager and send it as a bearer token to https://api.fireflies.ai/graphql. The webhook signing secret is a different credential, and live work requires network access.

Source text

SKILL.md · MIT
---
name: fireflies-webhooks-events
description: >-
  Implement a current Fireflies Webhooks V2 consumer with raw-body HMAC verification, event allowlisting, idempotency, ordering tolerance, and fast acknowledgement. Use when performing meeting lifecycle automation. Trigger with "Fireflies webhook v2", "meeting.transcribed event", or "verify Fireflies signature".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<repository-path> <workflow-scope>"
version: 1.12.0
license: MIT
author: Jeremy Longshore <[email protected]>
tags: [saas, fireflies, webhooks, events]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live Fireflies work requires network access"
---
# Fireflies Webhooks V2 Consumer

## Overview

Implement a current Fireflies Webhooks V2 consumer with raw-body HMAC verification, event allowlisting, idempotency, ordering tolerance, and fast acknowledgement.

## Prerequisites

- The target repository or integration path and the requested operator outcome.
- The Fireflies principal, team, environment, and data classification for the work.
- Current Fireflies documentation, credentials only when needed, and an accountable approver.

## Current Contract

V2 payloads contain event, timestamp, meeting_id, and optional client_reference_id. Documented events include meeting.transcribed and meeting.summarized. X-Hub-Signature is sha256=<hex HMAC> over the raw body; valid deliveries need a 2xx response within 10 seconds.

## Authentication

For authenticated operations, inject `FIREFLIES_API_KEY` from an approved secret manager and send it only as `Authorization: Bearer REDACTED_KEY` to `https://api.fireflies.ai/graphql`. Never print, commit, place in a URL, forward to a browser, or include the key in evidence. Webhook signing secrets are separate credentials and must not be reused as API keys.

## Instructions

1. Subscribe only to approved V2 event types at an HTTPS endpoint.
2. Capture raw bytes and validate the signature format and timing-safe HMAC before JSON parsing.
3. Validate event, timestamp, meeting_id, and optional client reference against a strict schema.
4. Reject unknown events or route them to a quarantined metadata-only lane.
5. Deduplicate using delivery metadata plus event and meeting identity, and tolerate summarized arriving after transcribed.
6. Acknowledge quickly, then fetch authorized data asynchronously if needed.
7. Record signature result, event type, latency, dedupe outcome, and job ID without payload content.

## Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, tests, and evidence. Use Write/Edit only for approved implementation or documentation changes. Do not query Fireflies, retrieve meeting content, create an AskFred thread, upload media, change account state, replay an event, or deploy merely because this skill was invoked.

## Approval Boundaries

Require approval before subscribing to team-wide events, fetching transcript content after an event, replaying a delivery, or retaining payloads.

## Output

Return the exact operation or event surface, environment, authorization class, selected field groups, validation results, content-free metrics, decisions, and a concise pass/fail receipt. Keep secrets and meeting-derived content out of general output.

## Validation

Before reporting success, rerun the smallest relevant deterministic check, compare actual state with the requested outcome and current contract, verify no secret or meeting-derived content entered logs or artifacts, and record unresolved uncertainty explicitly.

## Error Handling

- Missing signature when verification is configured: return 401.
- Duplicate delivery: acknowledge without repeating side effects.
- Unknown event: quarantine metadata and do not infer a schema.

## Examples

- "Review fireflies webhooks v2 consumer" produces a bounded plan and redacted receipt.
- A request that widens access or mutates production is paused at the approval boundary.

## Resources

Read [official Fireflies.ai evidence](references/official-docs.md) before relying on a field, filter, event, permission, plan limit, mutation, or processing state.

© Jeremy Longshore · MIT · jeremylongshore/tons-of-skills-marketplace

Similar skills

All skills for Backend and APIs →

From the same set139

The whole set →
long-polling-handler An auto-activating skill for long polling handler work in API integrations, with step-by-step guidance, generated code and configuration checks. CX Codex +1 1installs emitting-api-events emitting-api-events — a skill that builds event-driven APIs: outbound webhooks, Server-Sent Events, and message broker integration. Fits projects where mutations need to notify downstream services. CX Codex +1 1installs maintainx-webhooks-events maintainx-webhooks-events configures MaintainX webhook ingestion and work order event handlers in Express. Useful when connecting maintenance status changes to external systems. CX Codex +1 1installs lindy-webhooks-events The lindy-webhooks-events skill guides setup of Lindy AI webhook triggers and application callbacks. Use it to define event contracts, validate requests, and handle retries in a Lindy integration. CX Codex +1 1installs documenso-webhooks-events documenso-webhooks-events configures Documenso webhook endpoints and event handlers. Useful when tracking document signing status and automating downstream actions. CX Codex +1 1installs windsurf-webhooks-events The windsurf-webhooks-events skill guides you through building Windsurf extensions with the VS Code API and forwarding workspace events to an external service. Use it to track saves, editor changes, or terminal output. CX Codex +1 1installs twinmind-webhooks-events twinmind-webhooks-events — a skill for TwinMind meeting events: transcription completion, action item extraction, and calendar sync notifications. CX Codex +1 1installs firecrawl-webhooks-events firecrawl-webhooks-events sets up Firecrawl webhook ingestion with raw HMAC-SHA256 signature verification, deduplication, and polling fallback. CX Codex +1 1installs

Project sponsors

Companies that keep this analytics open