Skip to content
WaitForge
Open navigation
WaitForge

Collect the waitlist, verify interest, and launch from evidence.

Sign in Request beta access

Connect WaitForge

Connect your launch tools to one audience record.

Collect signups on a hosted page or your site. Then send approved audience data to APIs, webhooks, spreadsheets, and launch tools without rebuilding the list.

View the audience data path

WaitForge keeps the audience record in one place. Credentials and signing secrets stay server-side.

One audience record, four ways in

Every surface writes the same record, so a handoff never means a second list.

Connected
Hosted page and responsive embed
Browser
Signed lifecycle events, with replay
13 events
Expiring, scoped workspace tokens
Server
Spreadsheet handoff for a launch list
Export
The surfaces this workspace can publish today.
Team channels
Slack + Discord
Data handoffs
Sheets + Airtable
Open paths
Embed, API, webhooks
Secrets
Server-side only

Connect the journey without splitting the record.

Capture starts on the customer surface. WaitForge keeps the journey state. Each destination receives only the selected information.

Start with the center record. Then follow only the connection class your workflow needs.

Customer data path

One record controls every handoff.

Secrets remain server-side

01 · Capture surfaces

  • Hosted pageWaitForge surface
  • Responsive embedAllowed origin
  • Public APIOwned interface

02 · WaitForge source

The audience record

Identity, consent, answers, source, lifecycle state, and delivery evidence stay together.

Rule

A destination receives only the selected fields and events.

03 · Controlled destinations

Direct

Slack + Discord

Available now

Data handoff

Sheets + Airtable

Available now

Open interface

Signed webhooks

13 events

Open interface

Management API

Scoped access

HubSpot, Kit, GA4, and PostHog have no native bridge.

The record stays in WaitForge. Each connection has a separate setup, permission, and recovery boundary.

Choose how customer data enters and leaves.

Each path uses the same validation, identity, audience, and delivery state. Select the smallest interface that fits the product.

Fastest path

Responsive embed

Add one loader script and render the same validated signup experience inside your existing page.

  • Origin allowlist
  • Theme-aware form
  • Referral query support
Full interface control

Public + management APIs

Own the public UI, then manage campaigns and audience data with scoped Sanctum tokens.

  • Idempotent signup
  • Typed resources
  • Paginated audience
Reliable automation

Signed webhooks

Send lifecycle events to your stack with HMAC signatures, delivery history, retries, and replay.

  • Staged key rotation
  • Replay protection
  • Exponential retry

Know what connects before you design the workflow.

Start with what you want to move. Then check the support state, the information boundary, and the setup requirement.

Available now

Direct destinations

Connect a named destination from the workspace. Each path states its privacy and setup boundary.

Slack and Discord

Available now

Send selected launch signals to a team channel. Messages use aggregate data by default; identity needs an explicit opt-in.

Information moved
Campaign events, bounded counts, and an authenticated link back to WaitForge.
What you need
An incoming webhook URL and permission to manage workspace integrations.

Airtable

Available now

Write a selected audience into a snapshot or a maintained table. Maintained handoffs can update and remove records.

Information moved
Selected audience fields, eligibility state, and handoff evidence.
What you need
A personal access token, a base, and a compatible table.

Google Sheets

Deployment setup required

Write a selected audience into a snapshot or maintained worksheet after a workspace signs in to Google.

Information moved
Selected audience fields, eligibility state, and handoff evidence.
What you need
Google sign-in plus the deployment's configured OAuth and file picker.

Open interfaces

Build with protocols

Use a documented interface when the destination does not need a named adapter.

Responsive embed

Available now

Run the validated signup flow inside a page you already own.

Information moved
Submitted form fields, consent, referral context, and the resulting audience state.
What you need
One loader script and an allowed website origin.

Public and management APIs

Available now

Own the public interface or operate campaigns from an internal tool with scoped access.

Information moved
Campaign and audience resources allowed by the token scope.
What you need
A scoped, expiring token and an HTTPS client.

Signed webhooks

Available now

Push lifecycle events to an endpoint with delivery history, retries, and replay.

Information moved
13 documented lifecycle events with an HMAC signature.
What you need
A public HTTPS endpoint and signature verification.

Zapier, Make, and Pipedream

Via signed webhook

Use the automation platform's webhook trigger as the first step in a reviewed workflow.

Information moved
The signed lifecycle event selected in WaitForge.
What you need
A webhook trigger in the automation tool and a workflow owner.

Clear boundary

No native bridge

These names are common evaluation questions. WaitForge does not claim a native connector or a delivery date.

HubSpot and Kit

No native bridge

There is no provider-specific setup or managed synchronization today. Build a reviewed handoff with an available interface.

Information moved
Only what your API or webhook integration explicitly selects.
What you need
Your own integration through the API or signed webhooks.

GA4 and PostHog

No native bridge

WaitForge does not install an analytics destination or claim a native funnel synchronization.

Information moved
Only the events your own server integration chooses to forward.
What you need
Your own reviewed event mapping through an available interface.

A handoff remains controlled after setup.

Every connection names its credential. Webhook delivery also keeps the retry path and terminal failure visible.

Delivery retry schedule

Read from the delivery job, not a marketing estimate.

Up to 5 attempts
  1. 1Retry

    Immediate attempt

    A failure remains visible before the next attempt.

    Next wait · 1m

  2. 2Retry

    Attempt at 1m

    A failure remains visible before the next attempt.

    Next wait · 5m

  3. 3Retry

    Attempt at 6m

    A failure remains visible before the next attempt.

    Next wait · 30m

  4. 4Retry

    Attempt at 36m

    A failure remains visible before the next attempt.

    Next wait · 2.0h

  5. 5Final attempt

    Attempt at 2.6h

    A final failure remains visible and replayable.

A run that never succeeds stays failed and replayable in the delivery log.

Trust boundary

Each path names its credential.

The browser receives public presentation rules only.

Embed
Origin aware
API access
Scoped token
Webhook
HMAC SHA-256

No API token or webhook signing secret is exposed to the browser.

Connect the first customer path in three steps.

Use one controlled path. Verify the result before production traffic arrives.

  1. 01

    Create

    Create a campaign and choose its fields, origin rules, and verification mode.

    A live campaign surface

  2. 02

    Connect

    Copy the embed or create a scoped API token, then add an endpoint for events.

    One controlled handoff

  3. 03

    Verify

    Send a test signup, verify its signature, and inspect the delivery history before launch.

    A verified production path

Connect the customer journey to the systems that run it.

Start with the hosted page or embed. Add released APIs and automation without moving the audience later.

Request beta access