Send LeadsHook leads to Juiced

Before you start

• In LeadsHook: a decision tree with the form fields saved as custom fields. LeadsHook says it has no plans to choose from; billing is by impressions and the FAQ says you can use all advanced features (some at extra cost). The tree must be activated for webhooks to run.
• In Juiced: a source, a bearer token and the field names from View API Spec.

Step by step

1. 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 endpoint and field names. Details: setting up a source.

2. Add a Webhooks node after the form

   On the decision tree canvas, add a Webhooks node after the node that collects contact details, before the results page (how to use the Webhooks node). If you capture TrustedForm, place it late enough that the certificate has been created.

3. Set POST, the Juiced URL and JSON body

   Set the method to POST and the Payload URL to https://usejuiced.com/api/v1/leads. The body goes in the node's Data field as JSON (next steps). LeadsHook shows the other node settings only in screenshots, so labels may differ slightly in your account.

4. Add the headers

   Add three headers: Authorization with value Bearer plus one space plus your token, Content-Type with application/json, and Accept with application/json. LeadsHook's TrustedForm guide shows Accept and Authorization headers set on a Webhooks node, and it suggests proving the call in Postman first and copying working headers into the node (authorization and authentication).

5. Write the JSON with custom field merge tags

   In the Data field, write one top-level key per Juiced field title and a LeadsHook merge tag in curly braces as the value, inside double quotes: "first_name": "{first_name}". Separate pairs with commas and leave no comma after the last one (troubleshooting webhooks). Add |e164 to the phone tag if you want E.164 format (LeadsHook's HighLevel guide shows this filter). LeadsHook suggests checking the JSON in an online JSON editor before saving.

6. Activate the tree and test with a test zip

   Publish and activate the decision tree, then run through it with zip 00001 (expect accepted) or 00003 (expect rejected). In Juiced open Entries > Incoming logs, filter Test only, open the log and click Post to see the payload, response and validation errors. Turn off test mode on the source before going live.

Field mapping

The value side is your LeadsHook custom field name in braces. The key side is the Juiced field title.

LeadsHook captures a URL parameter when you create a text custom field with exactly the same name, such as utm_source (URL parameters). Add each extra field to your Juiced lead category or source first.

Example request

POST https://usejuiced.com/api/v1/leads
Authorization: Bearer <your token>
Content-Type: application/json
Accept: application/json

{
  "first_name": "{first_name}",
  "last_name": "{last_name}",
  "email": "{email}",
  "phone": "{mobile|e164}",
  "zip": "{zip}",
  "trusted_form_cert_url": "{xxTrustedFormCertUrl}"
}

Rename the merge tags to your own custom field names.

TrustedForm and Jornaya

LeadsHook documents both. For TrustedForm, you create a text custom field xxtrustedformcerturl, add the TrustedForm script at tree or global level above the closing body tag, and fire a save script on exit from a node (LeadsHook TrustedForm guide). Its examples write the field in lower case and the merge tag in mixed case, so use the exact name shown in your account. For Jornaya, you add the LeadiD script and a hidden text custom field leadid_token (LeadsHook Jornaya guide). Map each to a field you added in Juiced. See passing TrustedForm and Jornaya.

Troubleshooting

• Nothing reaches Juiced. The decision tree is not activated, or the Webhooks node sits on a path the test did not take.
• Juiced reads no fields. The Content-Type: application/json header is missing, or the JSON is invalid (a trailing comma or an unquoted merge tag). Validate the JSON and add the header.
• 401 Unauthorized. A space or line break came with the token, "Bearer " is missing, or the token was replaced more than 24 hours ago.
• 422 or an empty value. A merge tag does not match the custom field name, so it sent blank. Compare tags with your custom fields and keys with View API Spec.
• Empty TrustedForm field. The node fired before the certificate existed. Move the Webhooks node later in the tree.

More fixes in webhook troubleshooting.

Frequently asked