Agent skill · software engineering · jeremylongshore
instantly-webhooks-events
Register and operate Instantly webhooks with schema validation, idempotency, privacy, and recovery controls. Use when adding event-driven lead, email, campaign, or account processing. Trigger with "register an Instantly webhook", "handle Instantly lead events", or "recover missed Instantly events".
Why this skill is useful
Provides specific API commands and event handling patterns for Instantly's webhook system that the AI wouldn't reliably generate on its own.
What it needs
Requires instantly account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Instantly Webhook Operations Overview Build a receiver for documented Instantly event types without assuming an unpublished signature or retry contract. Record assumptions, evidence, approval state, and rollback ownership so another operator can reproduce the result. Prerequisites The target repository, Instantly workspace, environment, and accountable owner Current security, privacy, compliance, capacity, and change-control requirements An approved API v2 key only when a bounded live verification is necessary Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Instantly documentation and package metadata. Use Write or Edit only when implementation was requested and exact target files are known; never write credentials, lead data, email content, or unrestricted environment output. Current Contract Events include workspace, campaign, timestamp, eventtype, and optional lead/email/reply content. Custom labels may arrive as eventtype values. The API supports list, create, patch, delete, test, resume, event-type discovery, and delivery-event observability. Authentication Use an API v2 key as Authorization: Bearer <key> against https://api.instantly.ai/api/v2. Grant only the endpoint-specific scopes needed, inject the key from an approved server-side secret manager, and never print, persist, commit, or place it in a URL. Treat key creation, rotation, revocation, member changes, workspace delegation, and production access as owner-approved actions. Instructions 1. Fetch the live event-type list and select only required events. 2. Review the HTTPS destination, data classification, retention, and receiver owner. 3. Create the webhook with the exact documented fields and least-privilege scope. 4. Validate schema, workspace identity, timestamp bounds, payload size, and event-specific optional fields. 5. Deduplicate using a receiver-owned stable fingerprint and process asynchronously. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-webhooks-events