Skip to main content
Four pipelines, each written end to end: what arrives, what Hookie does with it, what your own service receives, and where Hookie stops. That last part is the one worth reading before you build anything. Hookie delivers a signed JSON event to a URL you own. Your service is what writes to your CRM, posts to Slack, or sends the email. Hookie does not talk to those products, and there is no configuration that makes it — a destination is one immutable HTTPS URL, one fixed body and one fixed header set, with no auth header and no body template.

Lead intake & AI qualification

A plain HTML form posts straight at an endpoint, a workflow scores the lead, and a branch delivers only the ones worth chasing.

Support ticket triage

Helpdesk webhooks land, an AI step assigns severity, and the urgent ones are escalated to your own service.

Billing & account lifecycle

Stripe events routed into datasets by kind, with dunning separated from provisioning.

Product-led onboarding

Signup and activation events drive a workflow that waits for the next step and nudges when it does not come.

​
What they have in common

Building one of these? hookie listen forwards the live events to your laptop while you write the handler, so you can develop against real payloads without deploying anything.