Send Growform leads to Juiced

Why Growform goes through Zapier or Make

Growform's Webhook integration sends every submitted field together with information about each field, a submission ID, the webhook version, the form ID and disqualificationReasons (Growform webhooks). Its docs do not describe a way to add an Authorization header or to rename keys, and Growform's own answer to posting to an external webhook is to use Zapier (Growform FAQ). Juiced needs top-level JSON keys and an auth header, so a connector sits in between.

Before you start

• Growform: a published form. Growform's plans are Basic, Professional, Scale and Custom; its pricing page lists TrustedForm and Jornaya on Professional, Scale and Custom. Check the pricing page for webhook and Zapier availability on your plan.
• Zapier or Make: Zapier's Webhooks by Zapier app, used for 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. Name every form field

   In the Growform builder, click each field, enter a name in the left-hand panel, and click Save. Unnamed fields show as (Unnamed field), and Zapier needs each name to be different (Growform field names). Naming fields after their Juiced keys, such as zip, makes mapping quicker.

3. Add hidden fields for UTMs

   With no field selected, click Hidden field in the field list and enter the parameter in hidden field name, for example utm_source. To fill it automatically instead, set hidden field type to preset and pick a value such as Page path, Referrer URL or gclid. Click save. Growform reads parameters such as ?utm_source=facebook on direct and embedded forms (Growform hidden fields).

4. Turn on TrustedForm or Jornaya

   Skip this if buyers do not ask for certificates. Go to Edit form settings, open Tracking & tagging, and enable TrustedForm, or enter your Jornaya campaign ID and account key, then click Save form settings. Submit a test and check View leads to see the value saved with the lead.

5. Start a Zap with the Growform New Form Submission trigger

   In Zapier, create a Zap, search for Growform and select Growform (Latest). Choose New Form Submission, click Sign into Growform and paste your API key from your Growform account page, then pick the form. If the form has no leads, submit one with Preview form, then click Test trigger (Growform and Zapier).

6. 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 Growform field to its Juiced key using the table below. The exact settings are in our Zapier guide.

7. Send a test lead and check Incoming logs

   Submit a test lead with zip 00001 and test the Zapier 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 switch the Zap on.

Using Make instead

Growform lists Make among its webhook destinations. In Make, add Webhooks > Custom webhook as the scenario's trigger, click Add, name it, click Save and copy the URL (Make webhooks). In Growform, open Edit form settings, click Add integration, select Webhook, paste the URL and save. Run the scenario and submit a test so Make detects the fields, then add an HTTP request that posts JSON to Juiced, as set out in our Make guide.

Field mapping

Zapier shows each Growform field by the name you gave it. Map them to the Juiced keys from View API Spec.

TrustedForm and Jornaya

Growform captures both natively. For TrustedForm, enable it under Edit form settings > Tracking & tagging; the certificate URL then appears in your results with each lead (Growform TrustedForm guide). For Jornaya, enter the account code from LeadiD's My account screen and the campaign key from Campaigns > My Campaigns, and optionally add a Jornaya TCPA Disclosure field (Growform Jornaya). Growform's docs do not name the keys these values use, so pick them from the Zapier sample and map them to trusted_form_cert_url and jornaya_leadid. Mark those fields Deliverable in Juiced if buyers need them. See passing TrustedForm and Jornaya to Juiced.

Troubleshooting

• The Zap stopped mapping a field. Renaming a Growform field can break an existing Zap. Check the Zap's fields and run a test after any rename.
• Some leads never reach Juiced. If Prevent disqualified leads being sent to Zapier, webhooks and email is on, disqualified leads stay in Growform's results only. Turn it off if you sell those leads too.
• Zapier finds no sample. The trigger loads the most recent lead. Submit one with Preview form, then click Test trigger again.
• The certificate field is empty in Juiced. Make sure TrustedForm or Jornaya is enabled in Tracking & tagging, the value shows in View leads, and the Juiced field exists on the source.
• 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