Send Salesforce leads to Juiced

Before you start

• Salesforce: admin access with the Customize Application permission to create credentials, External Services and flows. Salesforce introduced POST support for HTTP Callout as a beta, so check its status in your org.
• Juiced: a source for these leads, its bearer token, and the field names and example cURL from View API Spec. The example request becomes your sample request below.
• Zapier or Make route: a Salesforce edition with API access (Make notes that not all editions have it) and a Zapier or Make account.

Step by step

1. Create a Juiced source and copy a 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. Open Overview > More actions (⋯) > View API Spec for the endpoint and field names. Walkthrough: setting up a source.

2. Create the External Credential

   In Setup, enter Named in Quick Find, select Named Credentials, open External Credentials and click New. Give it a label such as Juiced, set Authentication Protocol to Custom and Save. Under Principals, click New and add a named principal with an authentication parameter that holds your Juiced token. Then add a custom header named Authorization whose value combines Bearer, a space, and that parameter. Salesforce documents that external credentials can carry custom headers (Named Credentials guide); check the exact header formula syntax in Salesforce Help for your org. Credential steps: Trailhead: create the credentials.

3. Create the Named Credential and grant access

   Back in Named Credentials, click New, set URL to https://usejuiced.com, select your External Credential and Save. Then create a permission set, open External Credential Principal Access, click Edit, move your principal to Enabled External Credential Principals, and assign the permission set to the users who will run the callout.

4. Create the HTTP Callout action

   In Flow Builder, add an Action and click Create HTTP Callout. Name the External Service and select your Named Credential. Set the method to POST and the URL path to /api/v1/leads. Under Provide Sample Request, click New, paste a short JSON body with your Juiced keys (see the example below), and click Review so Flow sets each key's data type. Add a sample response the same way (Juiced's reply nests id, status and price under data), then Done and Save. Steps from Salesforce's Flow HTTP Callout guide and Trailhead project.

5. Build the record-triggered flow on Lead

   Create a record-triggered flow on the Lead object that runs Only when a record is created. Add a Run Asynchronously path, which Salesforce recommends for sending requests to external systems (Trailhead: triggered flows). On that path, create a request body variable with the Apex-Defined data type and the External Service class ending in IN_body, add an Assignment that sets each key from the triggering Lead, then add your HTTP Callout action with that variable as its body.

6. Test with a test zip and check the log

   Save and activate the flow, then create a test Lead with the postal code 00001 (accepted) or 00003 (rejected). In Juiced open Entries > Incoming logs, filter Test mode > Test only, open the log and click Post to see the request and response. Then turn test mode off.

Field mapping

In the Assignment element, set each body key from the triggering record. Standard Lead fields:

Keys must match the field Title in Juiced exactly and must be in the sample request so Flow creates them. List of Values fields accept only their listed values, so match picklist values to them.

Example request

Use this as the sample request, then have the flow send the same shape. The Named Credential adds the header.

POST https://usejuiced.com/api/v1/leads
Authorization: Bearer <your token>
Content-Type: application/json

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

Troubleshooting

• The callout fails or is not offered on the immediate path. Move it to the Run Asynchronously path, which Salesforce recommends for requests to external systems.
• 401 Unauthorized. Check the custom header on the External Credential: Bearer, one space, then the token, with no line break. Also confirm the running user has the permission set with principal access. A new Juiced token expires the old one 24 hours later.
• 422 validation error. The response gives error.code and the field errors, and the Juiced log's Validation errors name the field. Often the Lead had no postal code, so zip was empty.
• A key never arrives. It was not in the sample request, so the External Service has no slot for it. Edit the External Service in External Services or recreate the action with the full sample.
• 201 but data.status rejected. Juiced received the lead but did not sell it. Open the log to see why.

More fixes: webhook troubleshooting.

Frequently asked