Send Tally leads to Juiced

Why Tally goes through Zapier or Make

Tally's native webhook posts JSON and lets you add HTTP headers, so the Authorization header is not the problem. The body is: each answer sits inside data.fields as an object with key, label, type and value, and Tally's docs describe no way to change that shape (Tally webhooks). Juiced only reads top-level keys such as email and zip, so a connector flattens each submission before it reaches Juiced.

Before you start

• Tally: a published form. The Zapier integration and hidden fields are free for all Tally users (Tally and Zapier, Tally hidden fields).
• 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.
• 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

   In the Tally editor, type /hidden to insert a Hidden fields block and add one field per value, such as utm_source and utm_campaign. Publish the form and copy its link from the Share tab. Pass values with ? before the first field and & between the rest, for example …/r/abc123?utm_source=facebook&utm_campaign=spring.

3. Start a Zap with the Tally New Submission trigger

   Open your published form's Integrations tab and connect Zapier, or start in Zapier: click + Create, choose Zaps, select Tally as the trigger app and New Submission as the event. Sign in to Tally, pick the form, and test the trigger to load a sample submission. Click Continue with selected record.

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 Tally 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 live form with zip 00001 and click Test step in Zapier. 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 in Zapier.

Using Make instead

In Make, start the scenario with the Tally Watch New Responses module. Connect with Tally OAuth, or with a personal API key created in Tally under Settings > API keys > Create API key and pasted into the connection's API Key field (Make's Tally 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 Tally field by its question label, and hidden fields by their names. Map them to the Juiced keys from View API Spec.

TrustedForm and Jornaya

Tally's help center does not describe TrustedForm or Jornaya support. TrustedForm's docs say its script must run inside the form's own page, and the form tool must allow custom JavaScript (TrustedForm iframe forms). Check with Tally and ActiveProspect before relying on certificates from a Tally 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 values are empty. Use the Hidden fields block. Tally notes that hidden fields are not the same as hiding a field's visibility. Also check the link starts the first parameter with ?.
• The Zapier webhook disappeared or will not delete. Connecting Zapier creates a webhook on the form's Integrations tab. Tally says webhooks created by an integration can only be removed in that integration, so manage it from the Zap.
• Zapier will not add a third step. Zapier's free plan supports two-step Zaps only, and the Webhooks by Zapier POST needs a paid plan.
• Zip codes lose their leading zeros. Collect the zip with a short answer field, not a number field.
• 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