Send ClickFunnels leads to Juiced
This guide sends every ClickFunnels form submission into a Juiced source. ClickFunnels webhooks send a fixed payload and the docs describe no custom headers, so the route is Zapier (or Make): a ClickFunnels trigger, then a JSON POST to Juiced.
Route: via Zapier or Make. Use the ClickFunnels Contact Submitted Form trigger in Zapier (or Watch form submission in Make), then POST the fields to Juiced as JSON.
You need an active ClickFunnels 2.0 account, a Zapier or Make account, and a Juiced source with a bearer token. The ClickFunnels app trigger does not need the Scale plan; native ClickFunnels webhooks do.
The gotcha: ClickFunnels' own webhooks wrap the contact inside a data object and cannot add an Authorization header, so pointing them straight at Juiced fails. Map each field to a top-level key in Zapier instead.
Why this goes through Zapier or Make
ClickFunnels 2.0 can send webhooks from Workspace Settings > Webhooks, but the request is a fixed JSON envelope (event_type, data, subject_id and so on) with the contact nested under data, and the docs give no way to add a custom header. Juiced needs your field names as top-level keys plus an Authorization header, so a connector sits in between. See ClickFunnels' webhooks article and developer webhook docs.
Before you start
- ClickFunnels: an active ClickFunnels 2.0 workspace with the funnel and form you want to send. The Zapier app needs only an active account. Native webhooks need the ClickFunnels Scale, Optimize or Dominate plan, but this guide does not use them.
- 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 (it is shown once). Then open Overview > More actions (⋯) > View API Spec for the endpoint and field names. Full walkthrough: setting up a source.
-
Connect ClickFunnels to Zapier
In ClickFunnels, click + Add Apps, select Zapier, then Log In and authorize. Or start in Zapier: create a Zap, pick ClickFunnels as the trigger app and click Sign in in the Account field. If you are already signed in to Zapier in the same browser, ClickFunnels reuses that session. Source: How to integrate Zapier with ClickFunnels.
-
Choose the Contact Submitted Form trigger
Set the trigger event to Contact Submitted Form. It fires when a contact submits any form, opt-in or order form. ClickFunnels' Zapier article says many triggers let you pick specific funnels and pages on the Trigger tab, or leave them blank to cover the whole workspace; check whether this trigger offers them in your account. Each Zap takes one trigger, so build one Zap per lead flow if you need different Juiced sources.
-
Pull in a test submission
Submit your live form once with test data, then click Test trigger, select the record and click Continue with selected record. Check which fields the record contains before you map anything.
-
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. The shared setup is on our Zapier guide. -
Test with a test zip and check the log
Send a test with
zipset to00001(accepted) or00003(rejected). 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. When it looks right, turn test mode off and publish the Zap.
Make's ClickFunnels 2.0 app has a Watch form submission trigger (plus Watch contacts). It connects with an OAuth client ID and secret from a platform application in the ClickFunnels developer portal. Follow it with an HTTP request module as shown in our Make guide. If you are still on ClickFunnels Classic, Make documents a separate Classic app and Classic funnel webhooks under the funnel's Settings > Manage Your Funnel Webhooks.
Field mapping
In the Webhooks by Zapier data rows, type the Juiced key on the left and pick the ClickFunnels field from the trigger on the right. Field labels in the trigger data depend on your form, so match them against your test record.
| ClickFunnels form field | Juiced key |
|---|---|
| First name | first_name |
| Last name | last_name |
email | |
| Phone | phone |
| Zip or postal code (required) | zip |
| Address, city, state | address_1, city, state |
| Custom questions | A key you created on the source's Fields tab, for example timeline |
| UTM values or other tracking | Keys such as utm_source, if they appear in your test record |
Keys must match the field Title in Juiced exactly. A key Juiced does not know shows in the post inspector but is not saved. List of Values fields accept only their listed values, so use a Zapier Formatter step if ClickFunnels answers use different wording.
TrustedForm and Jornaya
ClickFunnels' docs do not describe capturing a TrustedForm or Jornaya value. TrustedForm's script adds a hidden field named xxTrustedFormCertUrl to the form, per the TrustedForm Certify docs, but check in your account whether that value reaches the Zapier trigger data before relying on it. If it does, add a trusted_form_cert_url field (Type: URL) to the source, mark it Deliverable if buyers need it, and map it. More on passing consent certificates.
Troubleshooting
- The Zap does not fire. Check any funnel and page selections on the Trigger tab, and that the Zap is published.
- 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 missing or a key does not match a field Title. - Fields missing in Juiced. You probably pointed a native ClickFunnels webhook at Juiced. Its contact sits under
data, which Juiced does not read. Use the Zapier route. - Leads arrive twice on ClickFunnels Classic. Make warns that selecting several events on one Classic funnel webhook runs the scenario more than once, and that resubmitted forms can send duplicates from other pages. Choose one event and filter by page ID.
- 201 but
data.statusrejected. The lead was received but not sold. Open the log to see why.
More fixes: webhook troubleshooting.
Frequently asked
Does ClickFunnels have a webhook?
Yes. ClickFunnels 2.0 has webhooks under Workspace Settings > Webhooks on the Scale, Optimize and Dominate plans, but they send a fixed payload with the contact nested under data and the docs describe no custom headers, so use Zapier or Make to send leads to Juiced.
Can ClickFunnels send leads to a lead distribution platform?
Yes, through Zapier or Make. Trigger on Contact Submitted Form, then POST the fields as JSON with your Juiced bearer token, and Juiced routes each lead to buyers.
Which ClickFunnels plan do I need?
The ClickFunnels Zapier app needs only an active ClickFunnels account. Native webhooks need the Scale plan or higher. You also need a Zapier or Make account.
Which Zapier trigger should I use for ClickFunnels leads?
Use Contact Submitted Form. ClickFunnels says it fires when a contact submits any form, from opt-ins to order forms.
How do I pass a TrustedForm certificate from ClickFunnels?
ClickFunnels does not document capturing it. If the xxTrustedFormCertUrl value appears in your Zapier trigger data, map it to a trusted_form_cert_url field you add to the Juiced source.
Route ClickFunnels 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.