Send LeadCapture.io leads to Juiced
LeadCapture.io has a built-in Juiced option on each funnel's Lead Delivery tab. The route is Native: paste a Juiced token, map your fields to Juiced field names and switch it on.
Route: Native. Open the funnel's Lead Delivery tab, configure Juiced, paste your token, map fields and turn on Enable Juiced. No URL or header to set up.
You need a LeadCapture funnel (LeadCapture's pricing page says every plan includes all integrations) and a Juiced source with a bearer token.
Paste only the token, without the word Bearer, and replace LeadCapture's default keys with the exact Juiced field names. A default such as zip_postal does not match Juiced's zip.
Before you start
- In LeadCapture: a funnel. LeadCapture's pricing page says every plan includes all integrations, and its Juiced guide lists no extra plan requirement.
- In Juiced: a source, a bearer token from its Authentication tab, and the field names from View API Spec or the source's Fields tab.
LeadCapture publishes its own walkthrough: How to send leads from LeadCapture to Juiced. The steps below follow it.
Step by step
-
Create a Juiced source and copy a bearer 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). Open Overview > More actions (⋯) > View API Spec to see the exact field names. Details: setting up a source.
-
Open the Juiced option on Lead Delivery
Open your funnel in LeadCapture, go to the Lead Delivery tab, scroll to Juiced and click to configure it.
-
Paste the token
Paste the token into the API Token field and click Save. Paste only the token, not the word Bearer. LeadCapture adds the endpoint and header and sends JSON.
-
Map fields to Juiced field names
Open Field Mapping. For each field, type the exact Juiced field name in the Webhook Key box, then click Save. Map every field Juiced marks as required, and always map email and phone. Overwrite the grayed-out defaults where they differ, for example replace
zip_postalwithzip. For option questions, expand the field to remap the values each option posts if Juiced needs specific values. Skip fields your funnel does not use. -
Turn on TrustedForm if buyers need it
In the funnel's Settings tab, find the TrustedForm section (LeadCapture's articles place it under Compliance) and turn on Enable TrustedForm. LeadCapture captures the certificate automatically. Set the Certificate Field Name to your Juiced field name, then confirm the TrustedForm system field under Field Mapping.
-
Enable Juiced and save
Switch on Enable Juiced and click Save. Nothing is sent until you do. Send rules and Advanced Settings are optional; use them to send to more than one Juiced source on conditions.
-
Send a test lead and check both logs
Submit the funnel with zip
00001(Juiced assigns it) or00002(Juiced flags a duplicate). If OTP phone verification is on, enter the code or turn it off while testing. In LeadCapture, open the lead, then Webhook Deliveries > Juiced to see the request body and Juiced's response; use Resend, or Edit & Resend to change the payload first. In Juiced, open Entries > Incoming logs, filter Test only, open the log and click Post. Turn off test mode before going live.
Field mapping
In LeadCapture each row has a Webhook Key. Type the Juiced name into it.
| LeadCapture field | Webhook Key to enter |
|---|---|
| First name, Last name | first_name, last_name |
email | |
| Phone | phone |
Zip (default key zip_postal) | zip |
| Address sub-fields (street, city, state) | address_1, city, state |
| A qualifying question | The Juiced field title, such as timeline, with option values remapped to match a List of Values field |
| Hidden (UTM) fields, such as UTM: utm_source | A Juiced field you added, such as utm_source |
| TrustedForm system field | trusted_form_cert_url (add it in Juiced first) |
Hidden and UTM field rows are described in LeadCapture's field mapping guide. State fields can be sent full or abbreviated; match what your Juiced field expects.
Example request
LeadCapture builds the request for you. With the mapping above, Juiced receives:
Authorization: Bearer <your token>
Content-Type: application/json
{
"first_name": "Jane",
"last_name": "Smith",
"email": "jane@example.com",
"phone": "+15555550100",
"zip": "00001",
"trusted_form_cert_url": "https://cert.trustedform.com/..."
}
Check the exact body LeadCapture sent under the lead's Webhook Deliveries.
Fallback: the generic webhook
If you prefer a plain webhook, LeadCapture's webhook setup works too: on Lead Delivery click Add Webhook, paste https://usejuiced.com/api/v1/leads into Webhook URL, keep Payload Format on JSON, click Add Header and add Authorization with Bearer plus the token. Use the same Field Mapping keys. The payload is flat JSON, and it also includes system fields such as lead_id and ip_address (payload formats); Juiced does not save keys it has no field for. LeadCapture webhooks fire for partial leads as well as complete ones, so check what this webhook sends before going live.
TrustedForm and Jornaya
LeadCapture loads TrustedForm itself once Enable TrustedForm is on, and sends the certificate URL under the Certificate Field Name (default xxTrustedFormCertUrl), which applies to every integration on the funnel (LeadCapture TrustedForm docs). Set it to the field you added in Juiced. LeadCapture also offers Enable Jornaya LeadID in the Compliance area of Settings, with your Campaign Key. It sends the token as leadid_token unless you change Token Field Name; set that to a Juiced field such as jornaya_leadid (LeadCapture Jornaya docs). See passing TrustedForm and Jornaya.
Troubleshooting
- Unauthorized response. The API Token field contains "Bearer", a space or a line break, or the token was replaced in Juiced more than 24 hours ago. Paste a fresh token on its own.
- 422 for a missing field. A required Juiced field is not mapped or its Webhook Key is misspelled. Compare the keys with View API Spec, fix them and use Resend.
- Duplicate during testing. A repeat of an earlier test lead. Use a new email and phone, or zip
00001in test mode. - Nothing arrives in Juiced. Enable Juiced is off, or a send rule excludes the lead. Check the lead's Webhook Deliveries.
- 201 but status rejected. Juiced received the lead but did not sell it. Open the log in Incoming logs for the reason.
More fixes in webhook troubleshooting.
Frequently asked
Does LeadCapture.io integrate with Juiced?
Yes. LeadCapture.io has a built-in Juiced option on each funnel’s Lead Delivery tab. You paste a Juiced bearer token, map fields to Juiced field names and turn on Enable Juiced.
Do I include the word Bearer in LeadCapture’s API Token field?
No. Paste only the token. LeadCapture adds the Bearer prefix and the header itself.
Which LeadCapture.io plan do I need?
LeadCapture’s pricing page says every plan includes all integrations, and its Juiced guide lists no extra plan requirement.
Can LeadCapture.io send leads to a webhook instead?
Yes. Lead Delivery also has Add Webhook, with a JSON payload format and custom headers, so you can post to the Juiced leads endpoint with an Authorization header. The native Juiced option is simpler.
How do I pass a TrustedForm certificate from LeadCapture.io?
Turn on Enable TrustedForm in the funnel settings, set the Certificate Field Name to the field you added in Juiced, such as trusted_form_cert_url, and confirm it is mapped in Field Mapping.
Sell every LeadCapture lead to the right buyer
Juiced routes each incoming lead to buyers by their bids, caps and criteria, and sends leads that miss their first route 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.
