Send Granvl leads to Juiced

How Granvl delivers leads

Each Granvl funnel has a Delivery tab where you add destinations. Granvl's docs list GoHighLevel, HubSpot, ActiveCampaign, Zapier, Webhook, Formspree, Lead Prosper and Lead Distro AI (Granvl lead delivery). For Zapier and Webhook, Granvl has no field map: it sends the form "as it is, under your input names" and tells you to map fields in the receiving tool (Granvl field mapping). The Webhook destination expects a URL that accepts a form POST, and the docs describe no header settings. Juiced needs JSON with its own keys and an Authorization header, so Zapier or Make does the mapping.

Before you start

• Granvl: a published funnel with a form. Granvl's docs do not tie lead delivery to a plan; check your plan in your account.
• Zapier or Make: Zapier's Webhooks by Zapier app, used for the Catch Hook and the POST to Juiced, is on paid Zapier plans only (Zapier webhooks).
• Juiced: a source, its bearer token, and the field names from the source's View API Spec page.

Step by step

1. Create a Juiced source and 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 and copy it (it is shown once). Open Overview > More actions (⋯) > View API Spec for the endpoint and field names. See setting up a source.

2. Copy a Zapier Catch Hook URL

   In Zapier, create a Zap, click the Trigger step, select Webhooks by Zapier, choose Catch Hook from the Event dropdown, and click Continue. On the Test tab, click Copy to copy the webhook URL (Zapier catch hooks).

3. Add Zapier as a Granvl destination

   In Granvl, open Funnels, open the funnel, and select the Delivery tab. Under Add a destination, filter by Automation, select Connect → on the Zapier card, paste the Catch Hook URL into URL or embed code, and select Connect. Granvl says published pages pick up delivery changes automatically.

4. Submit a lead on the published funnel

   Open the live funnel and submit a lead with zip 00001. Do not use test drive: Granvl's troubleshooting guide says a test-drive submission intentionally does not reach your destinations (Granvl troubleshooting). In Zapier, test the trigger to load the lead and its field names.

5. Add a JSON POST to Juiced

   Add a Webhooks by Zapier action with the POST event. Set the URL to https://usejuiced.com/api/v1/leads, send the data as JSON, and add the Authorization, Content-Type and Accept headers. Map each Granvl input to its Juiced key using the table below. The exact settings are in our Zapier guide.

6. Check Incoming logs and go live

   Test the POST step. In Juiced, open Entries > Incoming logs, set the Test mode filter to Test only, open the log and click Post to see the request, any Validation errors and the response. When it shows Accepted, turn test mode off on the source and publish the Zap.

Using Make instead

In Make, add Webhooks > Custom webhook as the scenario's trigger, click Add, name it, click Save and copy the URL (Make webhooks). In Granvl's Delivery tab, connect the Webhook destination and paste the URL. Run the scenario, then edit the Webhook destination and click Send test lead so Make detects the fields (Granvl FAQ). Then add an HTTP request that posts JSON to Juiced, as set out in our Make guide.

Field mapping

Granvl sends your form inputs under their own names, and its docs say every lead carries a hidden granville_lead_id (Granvl lead tracking). Its docs do not list other values sent to destinations, so check the Zapier sample for UTM parameters or click IDs. Map them in Zapier or Make to the Juiced keys from View API Spec.

TrustedForm and Jornaya

Granvl's docs do not describe TrustedForm or Jornaya support. Check in your Granvl account or with Granvl before relying on certificates from a Granvl funnel. If you do capture a certificate URL or LeadiD, add a trusted_form_cert_url or jornaya_leadid field in Juiced and map the value to it, as covered in passing TrustedForm and Jornaya to Juiced.

Troubleshooting

• Nothing arrives in Zapier. Test-drive submissions do not reach destinations. Submit on the published funnel, and check the funnel has an enabled destination.
• A destination is not delivering. In the funnel's Delivery tab each destination should show Connected. Paused or Needs URL means it is not working. Hover a lead's pill in the Leads tab to see what happened at each destination.
• Field names do not match Juiced. Granvl sends inputs under their own names for Zapier and Webhook destinations. Rename keys in the Zapier or Make mapping, not in Granvl.
• You want a backup if delivery fails. Turn on Settings > Lead receipts > Keep sealed receipts to keep an encrypted copy of each submission for 21 days, then republish (Granvl lead receipts).
• 401 Unauthorized. The token was replaced (old tokens expire 24 hours after a new one is created) or the header has a stray space or line break.
• 422 or status rejected. A 422 has error.code validation_failed and errors names the field: a key does not match a Juiced field title or a value is not allowed. A 201 with data.status rejected means received but not sold. Open the log in Incoming logs. More fixes in webhook troubleshooting.

Frequently asked