Send HubSpot leads to Juiced

Before you start

• HubSpot: a Data Hub Professional or Enterprise subscription for the Send a webhook action, and Edit permissions for workflows (plus Publish to turn it on). HubSpot renamed Operations Hub to Data Hub, so older articles may use the old name.
• Juiced: a source for these leads, its bearer token, and the field names from View API Spec.
• Lower HubSpot tiers: a Zapier account. See the Zapier route below.

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 a workflow with a form submission trigger

   Go to Automation > Workflows (under More if shown) and create a contact-based workflow. Select When an event occurs, go to the Contact category, then Form, and select Form submission, and narrow it to your form with + Add criteria if the editor offers it. Click Done. Under re-enrollment, choose Yes, re-enroll every time the trigger occurs so repeat submissions are sent too, then Save. Source: Set event enrollment triggers.

3. Add a Send a webhook action

   Click the + icon, and under Data ops select Send a webhook. Set Method to POST and the Webhook URL to https://usejuiced.com/api/v1/leads. HubSpot's docs describe the POST body as JSON. Source: Use webhooks with HubSpot workflows.

4. Set the Authorization header

   Set Authentication type to API key. Enter Authorization as the API key name, set API key location to Request header, and in the API key dropdown select a secret whose value is Bearer, a space, and your Juiced token. HubSpot hides the key in test requests.

5. Customize the request body

   Choose Customize request body. For each Juiced field, enter the Juiced key as the Key and select the HubSpot property, using Add property for more rows. Use Add static value for fixed values such as a campaign name. Click Save.

6. Test with a test zip and check the log

   Expand Test action, enter property test values with the postal code set to 00001, and click Test. Review the Request and Response tabs. In Juiced open Entries > Incoming logs, filter Test mode > Test only, open the log and click Post. Then turn test mode off and turn the workflow on.

Field mapping

In HubSpot you pick properties by name, and each has an Internal name under Settings > Properties. Common defaults are below; confirm yours in your account.

Hidden fields: create a custom contact property, add it to the form as a hidden field, and fill it from the page URL with ?internalname=value, per HubSpot's query string article. Then map that property in the webhook body. Keys must match the Juiced field Title exactly, and List of Values fields accept only their listed values.

Example request

What HubSpot sends with a customized body. HubSpot's article does not list the Content-Type header it sends, so confirm the headers on the Request tab of Test action and in the Juiced post inspector.

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",
  "utm_source": "google"
}

TrustedForm and Jornaya

ActiveProspect does not publish a HubSpot-specific setup in the docs we reviewed. Its SDK adds a hidden field (default xxTrustedFormCertUrl, renamable), and the form must already be on the page when the script loads, per the TrustedForm Certify docs. Because embedded HubSpot forms render with JavaScript, check in your account that the certificate value is saved to a contact property before relying on it. If it is, map that property to a trusted_form_cert_url field on the Juiced source. See passing consent certificates.

Troubleshooting

• No Send a webhook action. It needs Data Hub Professional or Enterprise. Use the Zapier route on other tiers.
• 401 Unauthorized. The secret must read Bearer, one space, then the token, with no trailing space or line break, and the location must be Request header. A new Juiced token expires the old one 24 hours later.
• 422 and no retry. HubSpot does not retry 4XX responses (except 429). Read error.code and the field errors in the response or the Juiced log's Validation errors, fix the field, and re-enroll the contact.
• Fields missing in Juiced. You used Include all contact properties. Switch to Customize request body with Juiced keys.
• Repeat submissions not sent. Turn on re-enrollment for the form submission trigger.

More fixes: webhook troubleshooting.

Frequently asked