Agent skill · software engineering · jeremylongshore
fireflies-webhooks-events
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".
Why this skill is useful
Adds executable code for verifying HMAC signatures and processing Fireflies.ai webhook events, which is not commonly found in public documentation.
What it needs
Requires node installed locally. Requires fireflies account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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, meetingid, and optional clientreferenceid. 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 FIREFLIESAPIKEY from an approved secret manager and send it only as Authorization: Bearer REDACTEDKEY 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, meetingid, 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/fireflies-webhooks-events