---
title: Hubspot
slug: docs/hubspot
createdAt: 2026-04-21T19:43:22.304Z
---

#

HubSpot workflows allow you to send contact, company, or deal data to Jomablue in real time using the built-in webhook action. By configuring a workflow with a "Send a webhook" step, your team can automatically push registration or lead data from HubSpot to Jomablue as contacts are created, updated, or meet specific criteria.

This approach allows you to:

- Automate the transfer of registrants or leads from HubSpot to Jomablue as they register or qualify
- Reduce manual data entry and errors
- Track which records have been successfully sent

The instructions below cover setting up a HubSpot workflow, configuring the webhook action, mapping the payload, authenticating, and testing.

## Prerequisites

- **HubSpot Operations Hub Professional or Enterprise** — the "Send a webhook" workflow action requires this subscription tier
- A Jomablue ingest endpoint URL and bearer token (provided by Jomablue)

## 1. Create a Workflow

1. In your HubSpot account, navigate to **Automation → Workflows**
2. Click **Create workflow**
3. Choose **Contact-based** (or Company/Deal-based depending on your use case)
4. Select your enrollment trigger — for example:&#x20;
   - **When filter criteria is met** → Lifecycle stage is equal to "Subscriber" or a custom property like "Event Registration Status" is equal to "Registered"
   - **When an event occurs** → Contact fills out a specific form

## 2. Add the "Send a Webhook" Action

1. In the workflow editor, click the **+** icon to add an action
2. In the left panel, under **Data ops**, select **Send a webhook**
3. Set the **Method** to **POST**
4. Enter your Jomablue webhook URL:

:::BlockQuote
https\://yourinstance.jomablue.com/api/webhook/ingest/&#x7B;ingest\_endpoint\_uuid}
:::

## 3. Configure Authentication

HubSpot supports authenticating webhook requests using an API key in the request header. To configure this for Jomablue's bearer token:

1. Click the **Authentication type** dropdown and select **API key**
2. Set **API key name** to Authorization
3. Set **API key location** to **Request Header**
4. For the API key value, select or create a **HubSpot secret** containing your Jomablue bearer token in the format:

:::BlockQuote
Bearer eyJhbGciOi...
:::

:::BlockQuote
**Note:** The secret value must include the word Bearer followed by a space and then your token.
:::

## 4. Customize the Request Body

HubSpot gives you two options for the POST body:

- **Include all contact properties** — sends every property on the contact record. Jomablue can accept this and map the fields on our side, but it results in a larger payload.
- **Customize request body** *(recommended)* — lets you select specific properties and define the JSON key names sent to Jomablue. This is cleaner and easier to manage.

To use the recommended approach:

1. Select **Customize request body**
2. For each field, enter the **Key** (the JSON field name Jomablue expects) and select the corresponding **HubSpot property**

### Example Field Mapping

| Key                   | HubSpot Property                    | Description                         |
| --------------------- | ----------------------------------- | ----------------------------------- |
| organisation\_uid     | Record ID (or a custom external ID) | Unique identifier for deduplication |
| first\_name           | First name                          | Contact's first name                |
| last\_name            | Last name                           | Contact's last name                 |
| email                 | Email                               | Contact's email address             |
| company               | Company name                        | Contact's company                   |
| job\_title            | Job title                           | Contact's job title                 |
| mobile                | Mobile phone number                 | Contact's mobile number             |
| dietary\_requirements | *(custom property)*                 | Custom property for dietary needs   |

You can also add **static values** — for example, a static key source with value hubspot to tag the origin of the record.

### Example JSON Payload

Based on the mapping above, HubSpot will send a payload like this to Jomablue:

json

:::BlockQuote
\{  "organisation\_uid": "501",  "first\_name": "Jane",  "last\_name": "Doe",  "email": "jane.doe\@example.com",  "company": "Acme Corp",  "job\_title": "Marketing Manager",  "mobile": "+61400123456",  "dietary\_requirements": "Vegetarian",  "source": "hubspot"}
:::

:::BlockQuote
**Important:** HubSpot's customized request body produces a **flat JSON object** — nested fields are not supported natively. This is fine for Jomablue's ingest API, which accepts flat payloads and handles mapping internally.
:::

## 5. Test the Webhook

HubSpot provides built-in testing for webhook actions:

1. In the workflow editor, click on your **Send a webhook** action
2. Click **Test action**
3. Select a test contact (or enter test property values if using customized body)
4. Click **Test**
5. Review the **Request** and **Response** tabs to confirm:&#x20;
   - The request body contains the expected fields
   - Jomablue returns a 200 response with \{"success": true}

You can also test externally using webhook.site to inspect the exact payload HubSpot sends before pointing it at your Jomablue endpoint.

:::BlockQuote
**Tip:** Use the Jomablue test endpoint (POST /api/webhook/ingest/&#x7B;uuid}/test) to validate the payload against your configured mapping without persisting any data.
:::

## 6. Avoid Resending Records (Optional)

To prevent the same contact from being sent multiple times:

1. Create a custom contact property in HubSpot — e.g., sent\_to\_jomablue (single checkbox or boolean)
2. After the webhook action in your workflow, add an action to **Set contact property value** → set sent\_to\_jomablue to Yes
3. Add a filter to your enrollment trigger or a branch condition to skip contacts where sent\_to\_jomablue is already Yes

## 7. Error Handling (Optional)

You can add a **branch** after the webhook action to handle different outcomes:

- If the webhook succeeds (based on response status) → mark the record as sent
- If the webhook fails → send an internal notification, log to a list, or re-enroll for retry

HubSpot also provides workflow action logs under **Automation → Workflows → \[your workflow] → History** where you can review individual action executions and troubleshoot failures.

## Considerations

- Jomablue processes requests **asynchronously** — a 200 response means the request has been accepted and queued, not that processing is complete
- Use a stable unique identifier (such as the HubSpot Record ID or an external CRM ID) as the organisation\_uid to support deduplication on the Jomablue side
- HubSpot webhook payloads may send numeric-looking property values as integers rather than strings — Jomablue handles both formats
- The Jomablue ingest endpoint default rate limit is **120 requests per minute** — this is generally well within HubSpot's workflow execution rates, but be aware if you are bulk-enrolling large lists
