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
npx skills add jeremylongshore/tons-of-skills-marketplace --skill fireflies-webhooks-events -a claude-codeWhat 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-Signatureagainst the raw body before parsing - Quarantine unknown event types instead of guessing a schema
- Keep the handler idempotent when a delivery repeats
- Handle
meeting.summarizedarriving beforemeeting.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.summarizedhandler with idempotency keyed onmeeting_id.
How to install fireflies-webhooks-events
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill fireflies-webhooks-events -a claude-code2Manually: put the files in place
~/.claude/skills/fireflies-webhooks-events/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/fireflies-webhooks-events/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill fireflies-webhooks-events -a codex2Manually: put the files in place
.agents/skills/fireflies-webhooks-events/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill fireflies-webhooks-events -a cursor2Manually: put the files in place
.cursor/skills/fireflies-webhooks-events/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jeremylongshore/tons-of-skills-marketplace skills/.curated/fireflies-webhooks-events2Manually: put the files in place
.github/skills/fireflies-webhooks-events/SKILL.md1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill fireflies-webhooks-events -a gemini-cli2Platform CLI
gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace --path skills/.curated/fireflies-webhooks-eventsManually: put the files in place
.devin/skills/fireflies-webhooks-events/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill fireflies-webhooks-events -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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