Send Elementor form leads to Juiced

Why Elementor goes through Zapier or Make

Juiced needs a JSON body with its field names as top-level keys and an Authorization header. Elementor's Webhook action takes only a URL: Elementor's help center describes no header, format or body settings for it, and points you to Zapier as the usual destination (Integrate forms with Zapier). Elementor's developer docs list no documented filter for changing the webhook request (Elementor form hooks), so a connector is the supported path.

Before you start

• Elementor: Elementor Pro, which provides the Form widget and its Actions After Submit.
• Zapier or Make: Webhooks by Zapier needs a paid Zapier plan. In Make you use the Elementor app and an HTTP request module.
• 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. Set clear field IDs in the form

   Edit the page in Elementor and select the Form widget. For each field, open its Advanced tab and set the ID to the matching Juiced key, such as first_name, email or zip. Add a Hidden field for each extra value you want to pass, such as utm_source.

3. Create a Catch Hook in Zapier

   In Zapier, create a Zap, choose Webhooks as the trigger app and Catch Hook as the event, then continue and copy the webhook URL Zapier gives you.

4. Add the Webhook action in Elementor

   In the Form widget, under Actions After Submit, add Webhook. Open the Webhook section that appears and paste the Zapier URL. Save or update the page.

5. Submit a sample and test the trigger

   Open the live page, submit the form with zip 00001, then return to Zapier and test the trigger. Check that each field arrives with the name you expect. If you see an Advanced Data option on the Webhook action, turning it on adds field labels and form details to the payload.

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, add the Authorization, Content-Type and Accept headers, and map each Elementor field to its Juiced key. The exact settings are in our Zapier guide.

7. Send a test lead and check Incoming logs

   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, start the scenario with the Elementor Watch Forms module, save it and copy the webhook URL. In Elementor, choose Webhook under Actions after submit, paste the URL and click Update (Make's Elementor app). Then add an HTTP request that posts JSON to Juiced, as set out in our Make guide.

Field mapping

Zapier and Make show each Elementor field by its ID or label. Map them to the Juiced keys from View API Spec.

TrustedForm and Jornaya

Elementor has no TrustedForm or Jornaya setting. Add a Hidden field to the form and load the TrustedForm script on the page with its field variable set to that hidden field's name attribute, which you can read by inspecting the live form (TrustedForm Certify). For Jornaya, Verisk's WordPress guide fills a hidden input with the id leadid_token, or uses a callback that names your field (Jornaya for WordPress). Then map the hidden field in Zapier or Make to trusted_form_cert_url or jornaya_leadid, after adding that field in Juiced. More in TrustedForm and Jornaya.

Troubleshooting

• Zapier shows raw data instead of fields. Use the Catch Hook trigger, not Catch Raw Hook, and test again.
• Field names in Zapier are hard to recognize. Set each field's ID on its Advanced tab, submit a new sample, and remap.
• Pointing the Webhook action straight at Juiced fails. Juiced answers 401 because the action sends no Authorization header. Keep Zapier or Make in between.
• Zapier will not add the POST step. Webhooks by Zapier is on paid Zapier plans only.
• 422 or data.status rejected. A key does not match a Juiced field title or a value is not allowed. A 422 carries error.code validation_failed with errors keyed by field. Open the log in Incoming logs. More fixes in webhook troubleshooting.

Frequently asked