Send leads from Zapier to Juiced
This guide sets up the Zapier step that posts a lead into Juiced. It works with any trigger app, and every Juiced integration that runs through Zapier uses it for the final step.
Route: via Zapier. Any trigger app, then a Webhooks by Zapier POST action that sends JSON to https://usejuiced.com/api/v1/leads with your Juiced field names as keys.
You need a paid Zapier plan (Webhooks by Zapier is not on Free; it is on Professional, Team and Enterprise), a Juiced source and its bearer token.
The gotcha: if the Data section is left blank, Zapier sends every field from the trigger with the trigger app's names, and Juiced only saves keys that match its field titles. Fill in every row yourself.
Before you start
- In Zapier: a Professional, Team or Enterprise plan. Zapier lists Webhooks by Zapier as unavailable on Free (Zapier: send webhooks in Zaps). A working trigger step for the app your leads come from.
- In Juiced: a source, its bearer token (or API Key and API Secret for Basic auth), and the field names from View API Spec.
Building a Zap for a specific app? These guides cover the trigger side and link back here for the POST step: Facebook Lead Ads, Google Ads lead forms and TikTok lead ads.
Step by step
-
Create a source and copy a bearer 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 > Create token and copy it (it is shown once). Open Overview > More actions (⋯) > View API Spec for the endpoint and field names. Details: setting up a source.
-
Set up your trigger
Create a Zap and set up the trigger for your lead source, for example a new form submission or a new lead. Test the trigger so Zapier has a sample lead to map from.
-
Add the Webhooks by Zapier POST action
Add an action step, search for Webhooks by Zapier and choose POST in the Event dropdown. POST builds the request from the fields you enter, which is all Juiced needs. Zapier suggests Custom Request for cases such as nested JSON or highly customized headers, which Juiced does not use.
-
Enter the URL and choose JSON
In URL, enter
https://usejuiced.com/api/v1/leadswith no URL parameters. Set Payload Type to JSON. Do not use Form, which sends URL-encoded data Juiced does not read. -
Map each field in Data
In Data, add one row per field: the Juiced key on the left (typed exactly as in View API Spec, for example
first_name) and the mapped trigger value on the right. Click the plus icon for more rows. Always includezip. -
Add the headers
In Headers, add
Authorizationwith the valueBearer, one space, then your token. AddAcceptandContent-Type, bothapplication/json. To use Basic auth instead, leave out the Authorization header and fill the Basic Auth field with your API Key as the username and API Secret as the password,, in the format the field's hint shows. -
Test with a test zip code
Map or type
00001intozipfor the test, open the Test tab and click Test step. The test is live: Zapier really sends the request. The Data out tab shows Juiced's response, which should includedata.idanddata.status(acceptedfor zip 00001). In Juiced, open Entries > Incoming logs, filter Test mode to Test only, and open the log to see the payload as received. -
Publish and watch Zap history
Map
zipback to the real value, click Publish, then turn off Test mode on the Juiced source. Each run appears in Zap history; select a run and a step to see the data it received and sent, and replay runs that failed.
Field mapping
| Data row key (left) | Value (right) | Notes |
|---|---|---|
first_name, last_name | Mapped name fields | If the trigger gives one full name, split it with Formatter by Zapier or send it to a custom field. |
email | Mapped email | |
phone | Mapped phone | |
zip | Mapped zip or postal code | Always required. |
state, city, address_1 | Mapped address fields | Only if your lead category uses them. |
Custom key, e.g. roof_age | Mapped answer | Add the field on the lead category or the source's Fields tab first. List of Values fields accept only listed values. |
utm_source, trusted_form_cert_url | Mapped hidden field | Create these as fields in Juiced, then map them like any other row. |
Keys must match the field Title in Juiced exactly: letters, numbers and underscores, no spaces or dots. Zapier turns keys with double underscores (for example lead__zip) into nested objects, and Juiced does not read nested fields.
Example request
With Payload Type JSON and the rows above, Zapier sends:
POST https://usejuiced.com/api/v1/leads
Authorization: Bearer <your token>
Content-Type: application/json
Accept: application/json
{
"first_name": "Jane",
"last_name": "Doe",
"email": "jane@example.com",
"phone": "5555550100",
"zip": "00001"
}TrustedForm and Jornaya
Zapier only passes on what the trigger app captured. If your form records a TrustedForm certificate URL or a Jornaya LeadiD in a hidden field, add a matching field in Juiced (for example trusted_form_cert_url), mark it Deliverable if buyers need it, and map it in a Data row. See passing TrustedForm and Jornaya certificates.
Troubleshooting
- Webhooks by Zapier is locked. It is not available on the Free plan. Upgrade to Professional, Team or Enterprise.
- Unexpected fields in the log. If Data is blank, Zapier sends all fields from the previous step. Add explicit rows for each Juiced key.
- 401 Unauthorized. Check there is exactly one space after
Bearerand no line break in the token. A new token expires the old one 24 hours later, so update the Zap when you rotate tokens. - 422 with field errors. Read
error.codeand the fielderrors. A key is misspelled,zipis missing, or a List of Values field got a value that is not on the list. The Data out tab and the Juiced post inspector show which field. - 201 but data.status rejected. Juiced received the lead but did not sell it. Open the log in Incoming logs to see why.
- The Zap turned itself off. Zapier emails the account owner when a Zap errors on almost every run and can then turn it off (Zapier: Zaps that error). Fix the step, then publish again and replay failed runs from Zap history.
More fixes: webhook troubleshooting. Zapier references: testing steps, setting up an action, Zap history.
Frequently asked
Which Zapier plan do I need to send leads to Juiced?
A paid plan. Webhooks by Zapier is not available on the Free plan; Zapier lists it on Professional, Team and Enterprise.
Should I use POST or Custom Request?
Use POST with Payload Type JSON. Zapier builds the JSON from your Data rows. Custom Request sends exactly the text you type, so it is only worth it if you want to write the JSON by hand.
How do I add the Juiced bearer token in Zapier?
In the Headers section of the POST action, add a header named Authorization with the value Bearer, one space, then your token. You can use the Basic Auth field with your API Key and API Secret instead.
Why are my Zapier fields missing in Juiced?
Juiced saves only keys that exactly match a field title on the lead category or source. Check the spelling of each Data row key, avoid double underscores, and make sure the Data section is not blank.
Can I use Zapier to send leads from any app to Juiced?
Yes. Any app with a Zapier trigger can feed the same POST step, so the trigger is the only part that changes between apps.
Route every Zapier lead to the right buyer
Once leads reach Juiced, each one is routed to buyers by their bids, caps and criteria, and unsold leads can go to your marketplace.
Scale your lead business, without limits
Juiced puts you in full control of your leads, routing, and revenue, so you can automate, optimize, and grow without chaos.