What is a workflow blueprint?
A workflow blueprint is a dashboard-curated starting template that pre-configures a webhook for a common path — saving you from picking ingest channel, destination type, and transform from scratch on first use.
When you create a project, the dashboard surfaces blueprints organized around the most common shapes — different ingest channels, different destination types, different agent shapes. Pick one; the dashboard pre-fills the configuration; you fill in the destination URL and you're done.
What blueprints exist
Blueprints cover the cross-product of ingest channel and destination shape:
- HTTP-to-webhook flows — receive HTTP, deliver to your application's HTTP endpoint
- HTTP-to-queue flows — receive HTTP, deliver to AWS SQS
- HTTP-to-storage flows — receive HTTP, write events to S3-compatible object storage
- Email-to-webhook flows — receive email, deliver parsed JSON to your application
- Form-to-webhook flows — receive form submissions, deliver structured JSON
- Scheduled-to-webhook flows — fire a recurring trigger to your application
All tiers can see the blueprint catalog. Free projects can use the HTTP, email, and form paths; Starter unlocks scheduled webhooks; Pro and above also unlock the SQS and object-storage paths.
Why blueprints exist
Cold-start friction is the biggest barrier to value for any developer tool. Without blueprints, a new user has to learn the product's vocabulary (webhook, destination, transform, routing rule) before shipping anything. With blueprints, the dashboard says "you want to receive Stripe webhooks and forward them to your endpoint? Click this." The vocabulary comes after the first success, not before.
For the practical setup: Use workflow blueprints to ship an agent in minutes.
Frequently asked questions
Which blueprints does Hooksbase ship?
The cross-product of ingest channel and destination shape: HTTP to a webhook, HTTP to an SQS queue, HTTP to object storage, email to a webhook, form to a webhook, and scheduled to a webhook. Every tier sees the catalog; free projects can use the HTTP, email and form paths, Starter unlocks scheduled, and Pro and above unlock the SQS and object-storage paths.
Why do blueprints exist?
To remove cold-start friction. Without them a new user has to learn the vocabulary — webhook, destination, transform, routing rule — before shipping anything. With them the vocabulary comes after the first success rather than before it.
What is Hooksbase?
Hooksbase is event infrastructure for AI agents. It ingests events over four channels — HTTP, email, HTML form, and scheduled cron — verifies them, routes them by rule, runs versioned Automations in the event path, and delivers them to HTTP and cloud destinations (AWS SQS, AWS EventBridge, GCP Pub/Sub, and S3-compatible storage) with retries, strict ordering, Standard Webhooks-compatible signing, deterministic replay, and a dead-letter path. It is a hosted service, runs on Cloudflare Workers, is operated at hooksbase.com, and is not affiliated with — and shares no code or ownership with — other similarly named webhook, hook, or tunnelling tools.
Related terms
- Ingest
Accepting an event into Hooksbase via HTTP, email, form, or scheduled cron.
Read - Destination
A target URL or typed sink within a webhook; a webhook can have many.
Read - Webhook
An HTTP request one service sends to another to notify it that something happened.
Read - Attempt
One HTTP request within a delivery's retry chain.
Read