Ext Ops Panel
Open dashboard
Comparison

clawback vs zapier-webhooks

clawback is a plugin bundle for AI coding tools published by clawback-io. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). zapier-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclawbackzapier-webhooks
Claude Code: claude-plugins-community Listed
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Community marketplace hookdeck/webhook-skills Not listed Listed
Version: not stated
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

clawback vs zapier-webhooks
Factclawbackzapier-webhooks
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not published
Licence (differs)Not statedMIT
Repository (differs)github.com/clawback-io/clawbackgithub.com/hookdeck/webhook-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-21

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

clawback

In its own words, on Claude Code: claude-plugins-community:

Webhooks and cron scheduling for Claude Code. Receive events from external services like GitHub, Stripe, and Sentry, route them to the right session, and let Claude act on them automatically. Events are durably queued, delivered one at a time, and survive connection drops.

zapier-webhooks

In its own words, on Community GitHub marketplaces:

Receive and authenticate webhooks sent by the Webhooks by Zapier action (POST, PUT, Custom Request). Use when building an endpoint that a Zap calls, when asking how to verify a Zapier webhook signature (there is none: add an X-Webhook-Secret header or Basic Auth in the Zap and compare constant-time), when parsing the user-defined Form, JSON, XML or Raw payload, or when a Zap's webhook step shows as errored. Also points to Standard Webhooks verification for Zapier white-label connection webhooks, which are a separate product.

How to run each

clawback As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install clawback@claude-community

zapier-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install zapier-webhooks@webhook-skills

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: clawback · What it can do: zapier-webhooks · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built