GET api.eliasstravik.com /projects/greenware 200 OK

greenware

project · 200 OK · application/json

Website form lead routing for Clay-powered backend.

0★ Stars
0⑂ Forks
TSTypeScript
View on GitHub ↗
README.md

Route form leads through Clay without replacing your form or showing every visitor the same next step

Greenware lets you route each form submission through Clay while the visitor is still on your site when one static thank-you page cannot handle every lead, by attaching to the form you already use and rendering Clay's returned booking embed, redirect, message, or rejection in the browser.

✓ 100% free and open source ✓ One‑click Railway deploy ✓ Keep your existing form

⭐ Used by top GTM Engineers

Give every inbound lead the right next step while they are still on your site

Qualified buyers see a calendar where the form was. Other visitors receive the message, destination, or off-ramp meant for them before the context of the submission is lost.

Choose between static thank-you pages, form-builder rules, custom backends — or the form you already have connected to Clay

Greenware Static thank-you Form-builder rules Custom backend
Free software ✅ ✅ ❌ ✅
No backend code ✅ ✅ ✅ ❌
Keeps the existing form ✅ ✅ ❌ ✅
Routes with Clay enrichment ✅ ❌ ❌ ✅
Different action per lead ✅ ❌ ✅ ✅
Booking embed in the same form ✅ ❌ ✅ ✅
Signed single-use callbacks ✅ ❌ ❌ ✅
Tally and Typeform sessions ✅ ❌ ❌ ✅
One-click Railway deployment ✅ ❌ ❌ ❌

Keep the form your site already uses. Greenware manages the browser session, Clay makes the routing decision, and the visitor sees that action in place.

Submit the form. Let Clay decide what the visitor sees next.

📈 Move qualified buyers straight to the calendar

Return an embed or redirect action from Clay and let the visitor book while the reason they submitted is still fresh.

⚡ Let Greenware manage the wait

Greenware creates the session, sends the lead to Clay, accepts the signed callback, and returns the selected action to the same browser.

💬 Show the next step inside the form

Replace the submitted form with a calendar, redirect, message, or polite rejection as soon as Clay's callback arrives.

Route your first form through Clay in twenty minutes

1️⃣

Deploy Greenware
Use the Railway template, then add your Clay destination and allowed website origins.

2️⃣

Return an action from Clay
Add a final HTTP API column that posts the selected action to Greenware's callback URL.

3️⃣

Attach the form
Add the Greenware attributes and scripts, submit a lead, and watch the returned action replace the form.

Choose how to get started

Self-serve

For GTM engineers who manage inbound routing

Free

✓ Custom forms, Tally, and Typeform
✓ Multiple Clay destinations by form ID
✓ Redirect, embed, message, and reject actions
✓ Default UI or headless browser events
✓ Signed callbacks, read tokens, and origin checks
✓ Railway deployment with no database

Done-with-you

Hands-on setup and ongoing support for your GTM team

Let's talk

✓ Everything in self-serve
✓ Full setup and Railway deployment
✓ Clay webhook and callback configuration
✓ Greenware connected to your existing forms
✓ Team rollout, training, and best practices
✓ Ongoing maintenance and upgrades
✓ Dedicated Slack channel support
Deploy Greenware Book a demo

Get your questions answered

Do I have to replace my current form?

No. Greenware can attach to a custom-coded form or coordinate an existing Tally or Typeform embed.

Do I need to know how to code?

No code is needed to deploy the Railway template. A custom website form needs a small HTML snippet, while Tally and Typeform need hidden fields and a webhook URL.

What can Clay show after someone submits?

Four actions: redirect to an HTTPS page, embed a supported HTTPS calendar or iframe, show a message with an optional CTA, or show a polite rejection with an optional off-ramp.

Does Greenware store my form leads?

Greenware forwards the submission to Clay and keeps short-lived session state in memory. It does not use a durable database, and pending sessions disappear when the process restarts.

Can one deployment route more than one form?

Yes. Map form IDs to named Clay webhook destinations and keep a default destination for unmatched IDs.

Can I run several Greenware instances?

Not with the built-in store. Sessions and rate limits live in one process, so a multi-instance deployment would need shared storage.

Are allowed origins the same as server authentication?

No. Origin checks protect browser integrations from accidental cross-site use, but non-browser clients can forge that header. Provider flows use per-session hidden credentials, and callbacks use signed expiring URLs.

What does it cost?

Greenware is free and MIT licensed. You pay for the infrastructure, Clay, form provider, and enrichment services your workflow uses.

Route your first form through Clay in twenty minutes

A working form can route through Clay after one deployment and one small embed. Greenware handles the browser round trip. You connect the form and choose what Clay returns.

✓ 100% free and open source ✓ One‑click Railway deploy ✓ Keep your existing form

⭐ Used by top GTM Engineers