FAQ

Zapier is built for multi-step workflows across hundreds of apps—with branching, delays, and two-way sync. Hooks does one job: receive a webhook, optionally filter it, render a template, and deliver to your channels. The UI is smaller, the pricing is indie-friendly, and you are not paying for features you will never use. If you need “when X happens, do Y then Z across five tools,” use Zapier. If you need “when Stripe fires, post a clean message in Slack,” use Hooks.

Each tier has a monthly event limit (Free: 100, Pro: 5,000, Team: 50,000). When you hit the limit, new webhooks are accepted but not processed—you will see a clear banner in the dashboard. Upgrade to Pro or Team to resume processing. Existing stored events and replays follow the same quota rules documented on the billing page.

Every received event is stored with its raw payload. From the event detail page, click Replay to re-run the full pipeline: filter → template → delivery. A new event row is created linked to the original. Replays count toward your monthly quota and are rate-limited (100 per hour). You cannot replay a replay—replay the original event instead.

Yes. Signing secrets are encrypted at rest (AES-256-GCM). Payloads are stored on Supabase in the Tokyo region (ap-northeast-1). Row Level Security ensures you only see your own data. We do not sell or share your webhook data. Retention matches your tier (7 / 30 / 90 days). See Hooks Privacy Policy and Trust at TinyKomainu for full details.

At launch: Stripe, Shopify, and GitHub. Each has a dedicated receiver with signature verification and pre-built templates. Additional sources (e.g. Linear, Paddle) are post-MVP and will be prioritized based on user requests—tell us what you need at mk@natrium.co.jp.

Yes. Create a Slack Incoming Webhook for the channel you want, paste the URL into Hooks under Settings → Channels, then attach that channel to a route. No Slack app review required—setup takes about 30 seconds.

Hooks targets sub-second processing for the happy path: verify signature, persist the event, evaluate filters, render templates, and dispatch. The receiver responds to the source within a few hundred milliseconds; delivery to Slack or email usually completes within 1–2 seconds. Slow downstream channels (e.g. rate-limited APIs) may add more delay; check the delivery log on each event.

Yes. Add multiple routes on the same endpoint—each route is a filter + template + channel combination. For example, send all Stripe events to Slack, but only failed payments to email. Pro and Team tiers unlock Slack, Discord, and generic webhooks in addition to email.