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 relay'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.