Clay × ChiliPiper Sandbox

HubSpot form the “form” side

Region

Portal ID

Form ID (sandbox duplicate)

This is the duplicate form used only for the sandbox.

ChiliPiper routing the “routing” side

Routing mode

Concierge

ChiliPiper.deploy auto-hooks the form. Closest to prod.

Manual + enrich

ChiliPiper.submit with an explicit Clay-enriched lead.

Domain (subdomain of chilipiper.com)

Router (blank = concierge default)

Point this at a DUPLICATE sandbox router so no production routing fires.

Form type

Form IDs to hook (comma separated)

Clay enrichment edit & replay

Inject as hidden fields on the form Adds these keys as hidden inputs so the form submission (and concierge routing) carries the enriched data.

Enrichment payload (JSON) — simulates Clay output

In Manual mode this is merged into the ChiliPiper lead. Edits apply on the next submit — no reload needed.

Reference what maps where

Flow: HubSpot form submit → (Clay enrichment merged) → ChiliPiper router picks a rep → scheduler opens → meeting booked.

Concierge: ChiliPiper.deploy(domain, router, {formType, formIds}) — routing reads the submitted form.

Manual: ChiliPiper.submit(domain, router, {lead, map:true, domElement}) — you control the enriched lead object explicitly.

Config is saved to localStorage. “Apply & reload” re-initialises the form + ChiliPiper cleanly.

Sandbox loaded. Configure on the left, then submit the form below to watch the routing flow. Nothing here touches production unless you point it at production IDs.

Scripts

→

Form ready

→

Submitted

→

Enriched

→

Routed

→

Booked

HubSpot form

Loading form…

Event log 0 events

autoscroll

Clay × ChiliPiper / routing sandbox