Send Heyflow leads to Juiced
This guide connects a Heyflow flow to a Juiced source. The route is Via Zapier or Make: Heyflow triggers the scenario, and a JSON POST step sends each response to Juiced with flat keys.
Route: Via Zapier or Make. Heyflow's webhook puts every answer inside a fields object keyed by system label, and its body cannot be customized, so Juiced cannot read it directly.
You need a Heyflow flow on any plan (the Zapier app and Make connection are in the Core Bundle), a Zapier or Make account, and a Juiced source with a bearer token.
Send flat top-level keys that match your Juiced field titles. Posting Heyflow's raw webhook to Juiced loses every answer, because nothing is at the top level.
Why Heyflow needs Zapier or Make
Heyflow's webhook sends a flow ID, a response ID, a timestamp and a fields object such as "fields": { "System Label": "Value" }. Custom headers, basic auth and method choice are available on the Business plan, but the advanced webhook article says the payload structure is predefined and cannot be customized. Juiced needs each field as a top-level key, so the answers have to be remapped in between. Heyflow also lists LeadByte among its integrations, but not Juiced.
Before you start
- In Heyflow: a published flow with a clear system label on every input. The Zapier app and Make connection are in the Core Bundle on Basic, Pro, Agency and Business.
- A Zapier or Make account. Zapier needs a plan that includes Webhooks by Zapier.
- In Juiced: a source, a bearer token and the field names from View API Spec.
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. Open Overview > More actions (⋯) > View API Spec for the field names. Details: setting up a source.
-
Set the Heyflow trigger
Zapier: click Create Zap, search Heyflow and choose the New Response trigger. Click + Connect a new account, log in with your Heyflow email and password, then pick the flow. Make: add a Custom webhook module, copy its URL, paste it into Heyflow and click Connect, as Heyflow's Make guide describes. Make has no native Heyflow app.
-
Submit a full test response
Fill in every field of the flow and submit, with zip
00001. In Zapier click Test trigger; in Make, run the scenario once so it learns the structure. If the flow has conditional paths, test each path so every field appears. Add UTM parameters to the flow URL during the test, or they will not show up for mapping. -
Add the JSON POST to Juiced
Add a Webhooks by Zapier POST step, or an HTTP request module in Make, with URL
https://usejuiced.com/api/v1/leads, JSON payload, and headersAuthorization: Bearer <token>andAccept: application/json. The shared setup is in Zapier to Juiced and Make to Juiced. -
Map each answer to a Juiced key
In the data section, type each Juiced field title as a key (
first_name,email,zipand so on) and pick the matching Heyflow answer as its value. In Make, pick the values from inside thefieldsbundle. Use the table below. -
Test and check Incoming logs
Run the step, then in Juiced open Entries > Incoming logs, filter Test only, open the log and click Post to see the payload, response and any validation errors. Turn the Zap or scenario on, and turn off test mode on the source before going live.
Field mapping
Heyflow names each answer by the block's system label. Set labels you can recognize before you map.
| Heyflow value (by system label) | Juiced key |
|---|---|
| First name, Last name inputs | first_name, last_name |
| Email input | email |
| Phone input | phone |
| Zip or postal code input | zip (always required) |
| A multiple choice answer | The Juiced field title, such as roof_age; answers must match a List of Values field exactly |
| Hidden input fields and UTM parameters | Fields you added in Juiced, such as utm_source |
| TrustedForm certificate URL | trusted_form_cert_url |
| Jornaya LeadID | jornaya_leadid |
Add any extra field to your Juiced lead category or source first. Keys Juiced has no field for appear in the post inspector but are not saved.
TrustedForm and Jornaya
Heyflow has a TrustedForm integration under Integrate, Analytics tab, on the Business plan (Security Bundle). To pass the certificate on, Heyflow says to add a hidden input field whose variable name and system label match the TrustedForm setting, such as xxTrustedFormCertUrl (Heyflow TrustedForm docs). Its Jornaya Verisk integration (Pro, Agency, Business) creates a LeadID per submission that appears as a field you can select (Heyflow Jornaya docs). Map either value to a field you added in Juiced. See passing TrustedForm and Jornaya.
Troubleshooting
- Lead arrives with no fields. The Heyflow webhook was pointed straight at Juiced, so everything sat inside
fields. Route it through Zapier or Make and map flat keys. - A field is missing from the mapping list. The test response skipped it. Submit again filling every field and every conditional path, then retest the trigger.
- Mapping broke after editing the flow. Changing a system label changes the key Heyflow sends. Retest the trigger and remap the value.
- 401 Unauthorized (
unauthenticated). A space or line break came with the token, "Bearer " is missing, or the token was replaced more than 24 hours ago. - 422 with errors. A required key such as
zipis empty or misspelled. Compare with View API Spec. Juiced returnserror.codevalidation_failedwitherrorskeyed by field. - No TrustedForm URL. The hidden field's variable name does not match the TrustedForm setting, or an ad blocker stopped the script.
More fixes in webhook troubleshooting.
Frequently asked
Does Heyflow have a webhook?
Yes. Heyflow’s Hooks send each response to a URL. The payload nests answers inside a fields object, and its structure cannot be customized, so to send leads to Juiced you pass them through Zapier or Make.
Can Heyflow send leads to a lead distribution platform?
Yes. Heyflow lists LeadByte as an integration, and you can send responses to Juiced through Zapier or Make, where a JSON POST step maps each answer to a Juiced field.
Which Heyflow plan do I need?
The Zapier app and the Make connection are in Heyflow’s Core Bundle on all plans. Custom webhook headers need the Business plan, and TrustedForm needs Business. Juiced still needs a flat payload, so use Zapier or Make either way.
How do I pass a TrustedForm certificate from Heyflow?
Turn on Heyflow’s TrustedForm integration, add a hidden input whose variable name matches the certificate setting, such as xxTrustedFormCertUrl, then map that value to a field such as trusted_form_cert_url in your Zapier or Make POST step.
How do I pass a Jornaya LeadID from Heyflow?
Turn on Heyflow’s Jornaya Verisk integration on a Pro, Agency or Business plan. Heyflow adds a LeadID to each response, which you can map to a field such as jornaya_leadid in your Zapier or Make POST step.
Route every Heyflow 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.