← v17 index

Deploy from GitHub · /studio/build

paste repo URL → detect manifest → review actions → publish
v17 · Studio
DESKTOP · 1440px · AFTER DETECT SUCCEEDS · GITHUB SOURCE SELECTED
floom.dev/studio/build
studio Deploy new app
Read the deploy guide
DEPLOY AN APP

Paste a link. We handle the rest.

Point Floom at your GitHub repo or OpenAPI URL. We detect the manifest, turn every action into a runnable app, and give you a page at /p/:slug, an MCP endpoint, a JSON API, and a secrets vault. No Docker, no deploy config.

1. GitHub repo URL
TIP: private repo? Connect GitHub from Settings first, then paste.
2. Detected
floom.yaml found. 6 actions detected. COMMIT a9f3c21
repofloomhq/lead-scorer · main branch · public
manifestfloom.yaml · v1 schema
runtimehttp-proxy (no Docker build needed, backend already on https://api.lead-scorer.dev)
secrets neededOPENAI_API_KEY · CLEARBIT_API_KEY
slug (auto)lead-scorer · available
← change the slug in step 3 if you want a different URL
3
3. Pick which actions to expose
Uncheck anything you don't want visible on the public page. You can change this later.
score_lead
Score a single lead for fit + intent (0-100).
POSTpublic
score_batch
Score a CSV of leads in one call.
POSTpublic
enrich_company
Pull firmographics from domain.
POSTpublic
list_rubrics
List saved scoring rubrics.
GETpublic
admin_reindex
Rebuilds internal cache.
POSTprivate
healthcheck
Internal only.
GETprivate
4
4. Name, slug, description
Start private. Switch public when it's ready.
5
5. Preview the run surface
This is what visitors see on floom.dev/p/lead-scorer. Collapsed by default, expand to tweak the default renderer.
PREVIEW · default action: score_batch
▼ expand
leads: csv · required (company, domain, title, headcount)
rubric: enum[b2b-saas, agency, outbound] · optional
threshold: number 0-100 · optional
6
6. Deploy
target: floom.dev/p/lead-scorer
← secrets can be missing at deploy-time. They block the first run, not the publish.
LIVE BUILD LOG · streams during deploy
[00:00] detected floom.yaml · 6 actions · commit a9f3c21
[00:01] validating manifest…
[00:02] ✓ slug available · lead-scorer
[00:03] creating secrets vault · app_a9xkp2
[00:04] waiting for secrets OPENAI_API_KEY, CLEARBIT_API_KEY before first run
[00:05] ✓ public page live at floom.dev/p/lead-scorer
[00:05] ✓ MCP endpoint live at floom.dev/mcp/lead-scorer
[00:05] ✓ JSON API live at floom.dev/api/lead-scorer/*
[00:06] ready · add secrets to enable first run →
AFTER DEPLOY · SUCCESS STATE
STEP 6 OF 6 · DONE

lead-scorer is live.

Public page, MCP endpoint, and JSON API are up. Share the link to let anyone run it.

WHAT JUST HAPPENED
Manifest verified · 6 actions registered
Secrets vault created · app_a9xkp2
Deployed to floom.dev/p/lead-scorer · MCP + JSON API live
← button bounces once on load · confetti burst is a one-shot, not a loop
MOBILE · 390px
floom.dev/studio/build
Studio / Deploy
F
DEPLOY AN APP

Paste a link. We handle the rest.

GitHub repo or OpenAPI URL. We do the rest.

✓ 6 actions · lead-scorer
Needs: OPENAI_API_KEY, CLEARBIT_API_KEY
v17 notes
  • GitHub-first. Primary source is a repo URL with a floom.yaml. OpenAPI URL + raw paste are secondary tabs, one click away.
  • Six numbered steps. Detection auto-runs after URL paste (debounced). No submit button for detection — less friction.
  • Per-action visibility at deploy-time (step 3). Private actions are still reachable via API key but hidden from the public page.
  • Live build log pinned below the steps on desktop, collapsed into a log tab on mobile.
  • Missing secrets don't block deploy. They block the first run. The warn-coloured log line makes that obvious.
  • Supersedes build-flow-final.html (the ChatGPT-canvas draft from today, which used the wrong palette and type).