Templates / Automatically sync Beex leads to HubSpot (Create & Update)

Automatically sync Beex leads to HubSpot (Create & Update)

Unknown

by Beex ✓ · 128 views · created 2025-11-21 · CRM

Unknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.

Community nodes

These come from third-party npm packages. In n8n 3.0 unverified community packages are off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).

Nodes used (6)

What it does

Summary Automatically sync your Beex leads to HubSpot by handling both creation and update events in real time. How It Works 1. Trigger Activation: The workflow is triggered when a lead is created or updated in Beex. !11212.gif(fileId:3423) 2. Data Transformation: The nested data structure from the Beex Trigger is flattened into a simple JSON format for easier processing. !11211.gif(fileId:3422) 3. Email Validation: The workflow verifies that the lead contains a valid email address (non-null), as this field serves as the unique identifier in HubSpot. 4. Field Mapping: Configure the fields (via drag and drop) that will be used to create or update a contact in HubSpot. ⚠️ Important: Field names must exactly match the contact property names defined in HubSpot. !editfields.gif(fileId:3425) 5. Event Routing: The workflow routes the action based on the event type received: contactcreate or contactupdate. 6. Branch Selection: If the event is contactcreate, the workflow follows the upper branch; otherwise, it continues through the lower branch. 7. API Request Execution: The corresponding HTTP request is executed POST to create a new contact or PUT to update an existing one both using the same JSON body structure. Setup Instructions 1. Install Beex Nodes: Before importing the template, install the Beex trigger and node using the following package name: n8n-nodes-beex 2. Configure HubSpot Credentials: Set up your HubSpot credentials with: - Access Token (typically from a private app) - Read/Write permissions for Contacts objects !imagen10.PNG(fileId:3418) 3. Configure Beex Credentials: For Beex users with platform access (for trial requests, contact [email protected]): - Navigate to Platform Settings → API Key & Callback - Copy your API key and paste it into the Beex Trigger node in n8n !beexapikey.PNG(fileId:3420) !imagen12.PNG(fileId:3417) 4. Set Up Webhook URL: Copy the Webhook URL (Test/Production) from the Beex Trigger Node and paste it into the Callback Integration section in Beex. Save your changes. !imagen11.png(fileId:3419) Requirements - HubSpot: An account with a Private App Token and Read/Write permissions for Contacts objects. - Beex: An account with lead generation permissions and a Bearer Token configured in the Trigger Node. - Event Configuration: In the Beex platform's API Key & Callback section, enable the following events: - "Update general and custom contact data" - "Networking" !CAPTURE.PNG(fileId:3421) Customization Options - Contact Filtering: Add filters to control which Beex leads should sync to HubSpot. - Identifier Configuration: By default, only leads with a valid email address are processed to ensure accurate matching in HubSpot CRM. You can modify this logic to apply additional restrictions. - Field Mapping: The "Set Fields Update" node is the primary customization point. Here you can map Beex fields to HubSpot properties for both creation and update operations (see Step 4 in How It Works). - Field Compatibility: Ensure that Beex custom fields are compatible with HubSpot's default or custom properties; otherwise, API calls will fail due to schema mismatches.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.