Send Typeform leads to Juiced

Why Typeform goes through Zapier or Make

Typeform can post every response to a webhook, but the body is fixed: an event_id, an event_type and a form_response object whose answers sit in an answers array, with hidden fields in a nested hidden object. Typeform's webhook settings offer a Secret for signing but no custom headers (Typeform webhooks, example payload). Juiced reads top-level JSON keys and needs an Authorization header, so a connector sits in between and reshapes each response.

Before you start

• Typeform: a published form. The Zapier connection works with free or paid Typeform accounts (Zapier's Typeform guide). Typeform's dedicated UTM tracking is on Business plans or higher; on other plans pass UTMs as URL parameters.
• Zapier or Make: Zapier's Webhooks by Zapier app, used for the POST to Juiced, is on paid Zapier plans only (Zapier webhooks). In Make you use an HTTP request module; check your Make plan's limits.
• 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 URL parameters for UTMs

   Open your form, click Logic, then Pull data in. Click + Add new parameter for each value you want to carry, such as utm_source and utm_campaign, and click Save. Names must be lowercase with underscores. Typeform's example link passes values after a hash, for example …/to/abc123#utm_source=facebook (Typeform URL parameters). Labels may differ while Typeform tests new layouts.

3. Start a Zap with the Typeform New Entry trigger

   In Zapier, create a Zap, choose Typeform as the trigger app and New Entry as the event. Connect your Typeform account and pick the form. You can also start from Typeform: open the form's Connect panel, search for Zapier and click Connect (Typeform and Zapier). Connecting submits a placeholder test response to your form. Test the trigger to load a sample entry.

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 Typeform answer 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 live form with zip 00001 (or test the Zapier step with that value). 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 Typeform Watch Responses module, or the instant version listed as Watch Reponses (Instant), which asks you to click Create a webhook and then Create a connection (Make's Typeform 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 answer under its question, and URL parameters by name. Map them to the Juiced keys from View API Spec.

TrustedForm and Jornaya

Typeform's help center does not describe TrustedForm or Jornaya support. TrustedForm's docs say that for a form inside an iframe, the TrustedForm script must be placed in the iframe's own HTML, and the form tool must allow custom JavaScript (TrustedForm iframe forms). Check with Typeform and ActiveProspect before relying on certificates from a typeform. If your buyers ask for them, see passing TrustedForm and Jornaya to Juiced for how to add a trusted_form_cert_url or jornaya_leadid field.

Troubleshooting

• A placeholder lead appears. Connecting Zapier submits a placeholder response to your form. Keep the Juiced source in test mode until you have tested with a real submission.
• Your form is missing from the Zapier dropdown. Forms in a shared workspace only appear if you own them. Enter the form ID as a custom value instead.
• Leads arrive half filled. If Send partial responses to integrations is on, the trigger fires at each Partial Submit Point. Turn it off so only complete responses reach Juiced.
• UTM values vanished. Renaming a URL parameter that has already collected responses deletes those values. Create new parameters instead of renaming.
• 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