Send Formidable Forms leads to Juiced

Before you start

• Formidable: the Formidable API add-on, which needs the Business license or above (Formidable API).
• Juiced: a source, its API Key and API Secret from the source's Authentication tab, and the field names from View API Spec.
• Field IDs: note the ID of each field you will send. You use them as shortcodes such as [25].

Step by step

1. Create a Juiced source and copy its API key

   In Juiced, go to Ingest > Sources > New source, turn on Test mode, and click Create source. On the Authentication tab, copy the API Key and API Secret (they cannot be regenerated). Open Overview > More actions (⋯) > View API Spec for the endpoint and field names. See setting up a source.

2. Add a Send API Data action

   Open the form and go to Settings > Actions & Notifications. In the Misc tab, hover over Send API Data and click + Add. Give it an Action Name such as "Juiced".

3. Set the trigger, URL and Basic Auth

   Under Trigger this action when, select the entry being created. Set Notification URL to https://usejuiced.com/api/v1/leads. In Basic Auth, enter your API key, a colon, and your API secret, with no spaces.

4. Choose JSON and POST

   Set Data Format to JSON and Method to POST. Leave Character Set on its default unless your site needs another.

5. Map the key-value pairs to Juiced keys

   Add one key-value row per Juiced field. Type the Juiced key, such as email, and enter the field's ID shortcode, such as [25], as the value. Use the part shortcodes in the table below for Name and Address fields. Always include zip. Click Update.

6. Send a test lead and check Incoming logs

   Skip Test Connection, which only checks that the URL is reachable. Submit the live form with zip 00001. In Juiced, open Entries > Incoming logs, set the Test mode filter to Test only, open the log and click Post to see the request as received, any Validation errors and the response. When it shows Accepted, turn test mode off on the source.

Field mapping

Replace 10, 12 and so on with your own field IDs or keys. Formidable documents the part shortcodes on its Name field and Address field pages.

Example request

Formidable builds the Basic Auth header from the key and secret and adds a Content-type header by default.

POST https://usejuiced.com/api/v1/leads
Authorization: Basic BASE64_OF_API_KEY:API_SECRET
Content-Type: application/json

{
  "first_name": "Dana",
  "last_name": "Lee",
  "email": "dana@example.com",
  "phone": "5555550123",
  "zip": "00001",
  "utm_source": "facebook"
}

A 201 response with data.id, data.status and data.price means Juiced received the lead; data.status is accepted, rejected or duplicate (leads endpoint). To use a bearer token or add an Accept header instead, Formidable's docs point developers to the frm_api_request_args filter, which can change the request headers.

TrustedForm and Jornaya

ActiveProspect's Formidable guide adds the TrustedForm script in an HTML field directly above the submit button. The script writes the certificate URL into a hidden input named by its field variable, and the guide says to check Formidable saves that runtime field (TrustedForm for Formidable). One way to get a value you can send with a shortcode is to add a Hidden field and set the script's field variable to that field's input name. Neither guide documents this exact setup for Formidable, so confirm on your first test that the certificate URL reaches the post inspector. For Jornaya, Verisk's WordPress guide fills a hidden input with the id leadid_token, or uses a callback that names your field (Jornaya for WordPress). Map the hidden field to trusted_form_cert_url or jornaya_leadid after adding that field in Juiced. More in TrustedForm and Jornaya.

Troubleshooting

• 401 Unauthorized (unauthenticated). Basic Auth holds only the key, so Formidable sent :x as the password. Enter API_KEY:API_SECRET with the colon and no spaces.
• Test Connection fails or says dynamic URLs cannot be tested. It only checks the URL. Submit a real entry and check Juiced's Incoming logs, or Formidable's Logs add-on.
• Nothing is sent. Check Trigger this action when includes entry creation.
• Zip or name is empty. You used the whole Address or Name field shortcode. Use show="zip", show="first" and show="last".
• Nested data. Formidable suggests the Raw format for nested data such as repeaters. Juiced reads only top-level keys, so stay on JSON with one key per field.
• 201 with data.status rejected. Juiced received the lead but did not sell it. Open the log in Incoming logs to see why. More fixes in webhook troubleshooting.

Frequently asked