Send Jotform leads to Juiced

Why Jotform goes through Zapier or Make

Jotform's Webhooks integration posts each submission in Jotform's own structure: the answers arrive packed in a rawRequest value, and Jotform support says there is no setting to change the request's Content-Type or send a custom raw JSON body (Jotform webhooks, Jotform support answer). Jotform's webhook guide describes no header or authentication option. Juiced needs top-level JSON keys and an Authorization header, so a connector reshapes each submission first.

Before you start

• Jotform: a published form with the fields you sell. Jotform's Zapier guide does not list a plan requirement; check your plan's submission limits.
• Zapier or Make: Zapier's Webhooks by Zapier app, used for the POST to Juiced, is on paid Zapier plans only (Zapier webhooks). Make's Jotform trigger needs a Jotform API key with Full Access.
• 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. Add hidden fields for UTMs

   Add a Short Text field for each parameter, label it with the parameter name (for example utm_source), and set its Unique Name to the same value. Right-click each field and choose Hide so visitors do not see it. Values in the link, such as ?utm_source=facebook&utm_campaign=spring, then fill the fields, on the form URL or on the page where the form is embedded (Jotform UTM answer, Jotform URL parameters).

3. Start a Zap with the Jotform New Submission trigger

   In Zapier, click Create Zap, search for and select Jotform (or Jotform Enterprise), and choose New Submission from the Event dropdown. Connect your Jotform account, select the form, and test the trigger to load a submission, then click Continue (Jotform and Zapier).

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

5. Send a test lead and check Incoming logs

   Submit the form 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 click Publish Zap.

Using Make instead

In Jotform, open your profile's Settings, select API, generate a new key and give it Full Access; Make's docs say a key without it cannot create the webhook for an instant trigger. In Make, start the scenario with the Jotform Watch for Submissions module, create the webhook first, then create the connection and paste the key into API Key (Make's Jotform app). Then add an HTTP request that posts JSON to Juiced, as set out in our Make guide.

Field mapping

Zapier and Make list each Jotform field by its label, with sub-fields for name and address. Map them to the Juiced keys from View API Spec.

TrustedForm and Jornaya

Jotform support has said Jotform has no direct TrustedForm integration (Jotform support answer), and its help center does not describe Jornaya support. TrustedForm's docs say its script must run inside the form's own page (TrustedForm iframe forms). Check with Jotform and ActiveProspect before relying on certificates from a Jotform form. If your buyers ask for them, see passing TrustedForm and Jornaya to Juiced for the trusted_form_cert_url and jornaya_leadid fields.

Troubleshooting

• UTM fields arrive empty. The field's Unique Name must match the URL parameter exactly. For an embedded form, the parameters go on the page URL.
• Values arrive scrambled. Jotform's webhook docs say an encrypted form sends only encrypted data. Use an unencrypted form for leads you send to Juiced, or check with Jotform how encryption affects your integration.
• Make cannot create the trigger. Make's docs say this usually means the Jotform API key lacks Full Access. Update the key's permissions in Jotform's API settings and try again.
• You pointed Jotform's own webhook at Juiced. Juiced cannot read the rawRequest form data and the request has no Authorization header, so the post fails. Remove it and use Zapier or Make.
• 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