Send leads from Make to Juiced

Before you start

• In Make: a scenario with a working trigger module for the app your leads come from. This guide uses the current HTTP app; the older HTTP (legacy) app is covered at the end of the steps.
• In Juiced: a source, its API Key and API Secret (or a bearer token), and the field names from View API Spec.

App-specific guides that end with this step: Facebook Lead Ads, Google Ads lead forms and TikTok lead ads.

Step by step

1. Create a source and copy its credentials

   In Juiced, go to Ingest > Sources > New source, turn on Test mode and click Create source. Copy the API Key and API Secret from the Authentication tab, or create a bearer token there. Open Overview > More actions (⋯) > View API Spec for the endpoint and field names. Details: setting up a source.

2. Add the HTTP Make a request module

   After your trigger module, add the HTTP app and choose Make a request. Run the trigger once first so its fields are available to map.

3. Set the authentication

   Set Authentication type to Basic Auth and create a credential with your API Key as the username and API Secret as the password. Make recommends the Credentials field over putting secrets in headers. To use a bearer token instead, choose No authentication and add the Authorization header in the next step.

4. Enter the URL, method and headers

   Set URL to https://usejuiced.com/api/v1/leads and Method to POST. Under Headers, add Accept with application/json. Bearer token users also add Authorization with Bearer, one space, then the token.

5. Build the JSON body

   Set Body content type to application/JSON and Body input method to Data structure. Create a data structure with one item per Juiced key, then map a trigger value to each item. Make escapes reserved characters in values automatically. If you choose JSON string instead, you must escape values yourself, or build the body in a JSON > Create JSON module first and map its output into the body.

6. Turn on Parse response

   Set Parse response to Yes so Juiced's reply (data.id, data.status, data.price) can be mapped in later modules. In the advanced settings, Return error if HTTP request fails stops the scenario on a 401 or 422 so failures are not missed.

7. Run once with a test zip code

   Put 00001 in zip, click Run once and submit a test lead. Open the HTTP module's output to see the status code and response. In Juiced, open Entries > Incoming logs, filter Test mode to Test only, and open the log to see the payload as received.

8. Go live

   Map zip back to the real value, save and activate the scenario, then turn off Test mode on the Juiced source.

Field mapping

Item names must match the field Title in Juiced exactly and sit at the top level of the structure. Do not add collections: Juiced does not read nested objects.

Example request

POST https://usejuiced.com/api/v1/leads
Authorization: Basic <API Key:API Secret, base64>
Content-Type: application/json
Accept: application/json

{
  "first_name": "Jane",
  "last_name": "Doe",
  "email": "jane@example.com",
  "phone": "5555550100",
  "zip": "00001"
}

Make builds the Basic header from your credential. A mapped value that contains a double quote or a line break is what breaks a typed JSON string; the data structure method escapes it for you.

TrustedForm and Jornaya

Make forwards whatever the trigger captured. If your form stores a TrustedForm certificate URL or Jornaya LeadiD in a hidden field, add a matching Juiced field such as trusted_form_cert_url, mark it Deliverable if buyers need it, and map it in the data structure. See passing TrustedForm and Jornaya certificates.

Troubleshooting

• Invalid JSON errors. A mapped value contains a quote, backslash or line break in a typed JSON string. Switch to Data structure or use Create JSON.
• 401 Unauthorized. Check the Basic credential uses the API Key as username and API Secret as password, or that the bearer header has one space after Bearer. A new token expires the old one 24 hours later.
• 422 with field errors. Read error.code and the field errors. An item name does not match a Juiced field title, zip is missing, or a List of Values field got an unlisted value.
• Response fields not mappable. Set Parse response to Yes and run the module once.
• 201 but data.status rejected. Juiced received the lead but did not sell it. Open the log in Incoming logs to see why.

More fixes: webhook troubleshooting. Make references: HTTP app, JSON app.

Frequently asked