Send Webflow form leads to Juiced
This guide sends every submission from a Webflow form into a Juiced source. Webflow's form webhook nests the answers and its docs describe no way to add an auth header, so the route is Zapier (or Make): a Webflow form trigger, then a JSON POST to Juiced.
Route: via Zapier or Make. Use the Webflow New Form Submission trigger in Zapier (or Watch Events in Make), then POST the fields to Juiced as JSON.
You need a published Webflow site with a form that has received at least one submission, a Zapier or Make account, and a Juiced source with a bearer token.
The gotcha: Webflow sends answers under payload.data, keyed by each field's name, and its docs describe no custom headers. Juiced reads top-level keys and needs Authorization, so map each field in Zapier rather than pointing the webhook at Juiced.
Why this goes through Zapier or Make
Webflow's form_submission webhook posts a JSON body with triggerType and a payload object, and the submitted values sit inside payload.data under each field's name. The only headers Webflow documents are Content-Type, x-webflow-timestamp and x-webflow-signature, and webhooks created in the dashboard omit the last two. Juiced needs top-level keys and an Authorization header, so a connector sits in between. Source: Webflow's Working with webhooks.
Before you start
- Webflow: a published site with the form, and at least one submission on it. Webflow says a form must have received a submission before it can connect to a Zap.
- Zapier or Make: a Zapier account (Webhooks by Zapier is a paid Zapier feature) or a Make account.
- Juiced: a source for these leads, its bearer token, and the field names from View API Spec.
Step by step
-
Create a Juiced source and copy a token
In Juiced, go to Ingest > Sources > New source, turn on Test mode and click Create source. On the Authentication tab click New bearer token > Create token and copy it. Open Overview > More actions (⋯) > View API Spec for the endpoint and field names. Walkthrough: setting up a source.
-
Name your Webflow form fields
In the Webflow Designer, give each form field a clear name, ideally the Juiced key itself (
first_name,email,zip). Webflow keys submitted values by field name, so clear names make mapping simple. Publish the site and submit the form once with test data. -
Choose the New Form Submission trigger
In Zapier, create a Zap, choose Webflow as the trigger and select New Form Submission. Connect your Webflow account, choose the site from Site Name and the form from Form Name, click Continue, then click Test trigger and Continue with selected record. Steps from Webflow's Zapier help article (it labels the event Form submission).
-
Add the POST to Juiced
Add a Webhooks by Zapier action with the POST event. Set the URL to
https://usejuiced.com/api/v1/leads, the payload type to JSON, add one data row per Juiced field (table below), and add the headerAuthorizationwith the valueBearer, a space, and your token. Shared setup: our Zapier guide. -
Test with a test zip and check the log
Send a test with
zipset to00001(accepted) or00002(duplicate). In Juiced open Entries > Incoming logs, filter Test mode > Test only, open the log and click Post to see the request, any Validation errors and the response. Then turn test mode off and publish the Zap.
Make's Webflow app has a Watch Events webhook trigger; choose the form submission event (check the event list in your account), then add an HTTP request module as in our Make guide. Developers can skip the connector by receiving the Webflow webhook on their own server and reposting it, as covered in custom code.
Field mapping
In the Webhooks by Zapier data rows, type the Juiced key on the left and pick the Webflow field from the trigger on the right. Webflow shows each value under the field name you set in the Designer.
| Webflow form field (by name) | Juiced key |
|---|---|
| First Name | first_name |
| Last Name | last_name |
email | |
| Phone | phone |
| Zip (required) | zip |
| Select or radio answers | A key you created on the source's Fields tab |
| Hidden inputs (UTM values, landing page) | Keys such as utm_source, utm_campaign |
Hidden fields: Webflow's form elements have no hidden field type in the docs we reviewed. A common approach is an Embed element inside the form containing <input type="hidden" name="utm_source">, filled from the URL with a small script. Check the result in your Zapier test record before mapping it.
Keys must match the field Title in Juiced exactly. Unknown keys show in the post inspector but are not saved, and List of Values fields accept only their listed values.
TrustedForm and Jornaya
TrustedForm's script adds a hidden field named xxTrustedFormCertUrl to the form. ActiveProspect says to place the snippet just before the closing body tag, and that the form must already be on the page when the script loads, or the field is not added (TrustedForm Certify docs). On Webflow, add the script through custom code if your plan allows it, submit a test, and confirm the value appears in the Zapier trigger data. Then add a trusted_form_cert_url field (Type: URL) to the source and map it. See passing consent certificates.
Troubleshooting
- The form does not show in Zapier. Submit it once on the published site. Webflow needs at least one submission before a form can connect.
- Juiced returns 401 Unauthorized. The header must read
Bearer, one space, then the token, with no trailing space or line break. A new token expires the old one 24 hours later. - Juiced returns 422. Check
error.code(usuallyvalidation_failed) anderrors, or open the log: Validation errors name the field. Usuallyzipis empty or a key does not match a field Title. - Every field is missing. A Webflow webhook was pointed straight at Juiced. Its values sit under
payload.data, which Juiced does not read. - Field titles with spaces. Juiced field titles cannot contain spaces, so map Webflow's
First Nametofirst_namein Zapier.
More fixes: webhook troubleshooting.
Frequently asked
Does Webflow have a form webhook?
Yes. Webflow can send a form_submission webhook, but the answers are nested under payload.data and Webflow’s docs describe no way to add an Authorization header, so use Zapier or Make to send Webflow leads to Juiced.
Can Webflow send leads to a lead distribution platform?
Yes, through Zapier or Make. Trigger on New Form Submission, then POST each field as JSON with your Juiced bearer token, and Juiced routes each lead to buyers.
Why does my Webflow form not appear in Zapier?
Webflow requires at least one submission on the form before it can connect to a Zap. Submit the published form once with test data and test the trigger again.
How do I add hidden UTM fields to a Webflow form?
Webflow does not list a hidden field element, so a common approach is an Embed element inside the form with a hidden input, filled from the page URL by a short script. Confirm it appears in your Zapier test record.
How do I pass a TrustedForm certificate from Webflow?
Add the TrustedForm script to the page so it creates the xxTrustedFormCertUrl hidden field, confirm it shows in the Zapier trigger data, and map it to a trusted_form_cert_url field on the Juiced source.
Route Webflow leads to the right buyer
Juiced routes each lead to buyers by bids, caps and criteria, and leads no buyer takes can go to your marketplace.
Scale your lead business, without limits
Juiced puts you in full control of your leads, routing, and revenue, so you can automate, optimize, and grow without chaos.
