v2.2 Build Department
forge.wibiz.ai — pending DNS
1
Drop Onboarding Doc
2
Atlas Blueprints
3
Human Approves Manifest
4
Deploy Schema Scripts
5
Specialists Execute
6
Ward QA + Signal Launch
AI Specialists
9 online
Schema Scripts
6 ready
Vertical Templates
5 loaded
Playbooks
5 loaded
Active Builds
0
forge.wibiz.ai
Pending DNS

Launch a Build

Upload or paste the completed onboarding form. Atlas reads it and produces a single Build Blueprint — with every task labelled API, Manual, or Playwright.

📄

Drop onboarding document here

Supports .txt, .md, .pdf, .docx — content extracted automatically.

▶ Build Blueprint — ATLAS

Sub-account Connection Validator

Validate GHL credentials before any build work starts

Token is sent once to GHL for validation only. It is never stored in Forge — not in localStorage, not on the server.

Active Builds

Track build status — no API keys stored here

No builds tracked yet. Add your first build above.

Schema Deployment Scripts

Run these to auto-create custom fields, tags, and pipelines in a GHL sub-account via API

# One-time setup (per machine) cd "07 Forge/scripts/deploy_schema" && npm install # Per build: copy .env.example → .env, fill in API_KEY and LOCATION_ID # Then run base first, then the vertical: node base_schema.js # Universal WBZ_ fields — every build node restaurant_schema.js # Then the vertical script
Base Schema
API
11 universal WBZ_ fields + 10 standard tags. Run on every build before the vertical script.
node base_schema.js copy
Restaurant
APIHSKD
7 fields, 5 tags, 6-stage pipeline. Includes allergen flag. Nick sign-off required before Signal Launch.
node restaurant_schema.js copy
Spa & Wellness
API
9 fields, 5 tags, 7-stage pipeline. Health flag never stores the condition — flag only.
node spa_schema.js copy
Gym & Fitness
API
7 fields, 6 tags, 7-stage pipeline. Trial-to-membership funnel fields included.
node gym_schema.js copy
Real Estate
APIHSKD
10 fields, 8 tags, 9-stage pipeline. Legal flag pauses AI. Nick sign-off required.
node real_estate_schema.js copy
Tutoring
APICOPPA
8 fields, 6 tags, 8-stage pipeline. Minor flag and safeguarding flag included.
node tutoring_schema.js copy

QA Tools

Inspect workflows, fire test contacts, and debug live webhook payloads

Token used for live API calls only — never stored in Forge.
🔍 Workflow Inspector
List all workflows on the sub-account with status, trigger type, and last modified. Instantly shows deactivated workflows — the most common "trigger not firing" cause.
Test Trigger
Creates a disposable test contact tagged WBZ_QA_TEST and enrolls it in the selected workflow. Confirms end-to-end firing without touching real contacts.
No workflow selected — run Inspector first or paste a Workflow ID below
📡 Webhook Echo
Point any GHL webhook at the URL below. All incoming payloads appear here in real time — see exactly what GHL sends and whether the data matches what Make expects.
Listening for payloads…
Start listening, then trigger a GHL action to see the payload here.

The Build Blueprint — one document, full team execution

Atlas produces a single Build Blueprint with every task labelled: [API] automated now, [Manual — GHL] DEX must click, [Playwright] script handles it, [Blocked] waiting on client.

Add Build

# BUILD BLUEPRINT — STRUCTURE REFERENCE _One document. Every task labelled. Your team executes from this._ --- ## 1. CLIENT SUMMARY Name / Plan / Vertical / Channels / Languages / AI Authority Level / Escalation Contact ## 2. HSKD STATUS Flag: YES / NO. If YES: certification scenarios, Nick sign-off required. ## 3. TEAM ACTIVATED | Specialist | Activated | Reason | ## 4. TASK LIST — LABELLED [API] — schema scripts handle this automatically [Manual — GHL] — DEX must complete in GHL UI [Playwright] — Playwright script handles this [Make] — CRUZ builds a Make scenario [Manual — External]— action on non-GHL platform [Blocked] — waiting on client info ## 5. CUSTOM VALUES All wbz_ custom values with exact text content for this client. ## 6. SCHEMA SUMMARY Confirm: base_schema.js + [vertical]_schema.js. List any modifications beyond the standard template. ## 7. CORE WORKFLOWS Each workflow: name, trigger, purpose. ## 8. INTEGRATIONS Each Make scenario or webhook CRUZ must configure. ## 9. KB BRIEF FOR SAGE FAQ count / Subject areas / Escalation categories / HSKD rules. ## 10. QA CHECKLIST FOR WARD Minimum test matrix rows for this specific build. ## 11. SIGNAL LAUNCH GATE Exact conditions — screenshot-verified — before Signal Launch fires.