instantly-webhooks-events — Claude Code skill: setup and features
instantly-webhooks-events guides the setup and operation of Instantly API v2 webhooks with schema checks, deduplication, and privacy safeguards.
MIT 1 installs ★ 2,935 updated 2026-10-29
npx skills add jeremylongshore/tons-of-skills-marketplace --skill instantly-webhooks-events -a claude-codeWhat instantly-webhooks-events does
This skill structures the receiver for Instantly API v2 events, covering email bounces, campaign updates, and inbound lead replies. It enforces payload validation, workspace tenant matching, and timestamp boundaries. Deduplication relies on a receiver-owned stable fingerprint before passing events to background processing queues.
Strict approval boundaries prevent silent infrastructure changes. The agent cannot create or revoke tokens, attach sending accounts, modify campaigns, or register live webhooks without direct owner confirmation. It maps requests to https://api.instantly.ai/api/v2 using endpoint-specific scopes.
Running live verification requires network connectivity and an approved Instantly API v2 key.
What it helps with
- register Instantly API v2 webhook endpoints with least-privilege scopes
- validate incoming lead and campaign event payloads against schema rules
- prevent duplicate processing with stable receiver-owned event fingerprints
Example prompts for the agent
- Register an Instantly webhook for
email_bouncedandreply_receivedathttps://example.invalid/hook - Handle Instantly lead events with schema validation and deduplication
- Check the error handling plan for Instantly 429 rate limits and 401 auth failures
How to install instantly-webhooks-events
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill instantly-webhooks-events -a claude-code2Manually: put the files in place
~/.claude/skills/instantly-webhooks-events/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/instantly-webhooks-events/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill instantly-webhooks-events -a codex2Manually: put the files in place
.agents/skills/instantly-webhooks-events/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill instantly-webhooks-events -a cursor2Manually: put the files in place
.cursor/skills/instantly-webhooks-events/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jeremylongshore/tons-of-skills-marketplace skills/.curated/instantly-webhooks-events2Manually: put the files in place
.github/skills/instantly-webhooks-events/SKILL.md1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill instantly-webhooks-events -a gemini-cli2Platform CLI
gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace --path skills/.curated/instantly-webhooks-eventsManually: put the files in place
.devin/skills/instantly-webhooks-events/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill instantly-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 instantly-webhooks-events
How to install instantly-webhooks-events in Claude Code?
Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill instantly-webhooks-events -a claude-code in your terminal.
What does instantly-webhooks-events do?
It guides the creation and maintenance of Instantly API v2 webhook receivers with schema enforcement, idempotency, and access controls.
Is an Instantly API key required to use this skill?
Drafting code and validating payload schemas does not require credentials. An API v2 key is needed only for live network verification against the Instantly API.
Source text
SKILL.md · MIT
--- name: instantly-webhooks-events description: >- 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". argument-hint: "[receiver-url] [event-set]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.13.0 author: Jeremy Longshore <[email protected]> license: MIT tags: - saas - instantly - webhooks-events model: inherit effort: high compatibility: Designed for Claude Code; live verification requires network access and an approved Instantly workspace and API v2 key --- # 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, event_type, and optional lead/email/reply content. - Custom labels may arrive as event_type 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. Use test, delivery-event aggregates, and resume only with explicit change approval. ## Approval Boundaries Do not create, rotate, reveal, or revoke keys; invite or remove members; delegate across workspaces; connect sending accounts; create or activate campaigns; import or delete leads; change suppression or retention; register, patch, resume, or delete webhooks; alter plans or paid capacity; transmit diagnostics; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested. ## Output Return the workspace-safe scope, files and contracts inspected, exact API v2 routes and required scopes, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action. ## Error Handling | Condition | Response | |---|---| | `401` | Stop and verify that the bearer key exists, is current, and was not revoked. | | `403` | Stop and compare the operation with its exact required scope; do not broaden to `all:all` by default. | | `429` | Coordinate the workspace-wide budget, honor endpoint overrides, and bound retries. | | Schema or tenant mismatch | Fail closed, preserve redacted evidence, and do not retry a mutation. | ## Examples Use a compact handoff that makes scope, mutation authority, and evidence reviewable. Input: ```text events=email_bounced,reply_received; receiver=https://example.invalid/hook ``` Expected handoff: ```text registration=planned; signature=not-assumed; approval=required ``` ## Resources - [Skill-specific official documentation](references/official-docs.md) - [Instantly API v2 documentation](https://developer.instantly.ai/) - [Instantly API v2 OpenAPI document](https://api.instantly.ai/openapi/api_v2.json)
© Jeremy Longshore · MIT · jeremylongshore/tons-of-skills-marketplace