Integrations

How the Platform sits with HARMONiQ and HubSpot
NB Nathan General Manager
Workspace
NB Nathan Barnes General Manager The whole picture. On schedule, at risk, and what it is worth. AB Archie Barnes Production Manager What to build, in what order, at which station, and what will stop him. GB Grant Barnes Sales Manager The order book, the dealer channel, and how the integration actually works. DB Dallas Barnes Marketing Manager Campaigns, enquiries, and where the demand is coming from.
Persona is a lens, not a lock. Switching changes the dashboard and the landing page; it never hides a row.

How the Platform reaches HARMONiQ

HARMONiQ runs on premise, on Farmgear's own SQL Server, supported by Micronet. Nothing about that changes. The Platform connects to it through a Cloudflare Tunnel installed on the Farmgear network.

The tunnel makes an outbound connection only. No inbound port is opened on the Farmgear firewall, no VPN is required, and nothing about the SQL Server is exposed to the internet. Reads are made through a scoped SQL service account that can see the tables listed below and nothing else.

Writes go back the same way, into the same tables HARMONiQ already uses for works orders, stock movements, finished goods receipts and purchase requisitions. The Platform does not keep a competing set of books: it holds the production plan, which today lives in nobody's system.

HubSpot is a straight API integration on Farmgear's own private app token. Reads are on a schedule; writes are made at the moment the event happens, which is why a confirmed order shows on the deal within seconds rather than at the next sync.

The path
  1. 1Farmgear network
    HARMONiQ on SQL Server, on premise
  2. 2cloudflared connector
    outbound only, no inbound firewall rule
  3. 3Cloudflare Tunnel
    authenticated, encrypted end to end
  4. 4The Platform
    reads on a schedule, writes on the event

HARMONiQ

HARMONiQ
Micronet Systems, on premise SQL Server, over the Cloudflare Tunnel
EntityDirectionRecordsLast runStatusThis session
Product master and hierarchy into the Platform 120 7 Sep 19:18 OK, no change —
Bills of material into the Platform 970 7 Sep 19:18 OK —
Stock on hand by item and location into the Platform 452 7 Sep 19:36 OK —
Open purchase orders into the Platform 26 7 Sep 19:36 OK —
Open sales and dealer orders into the Platform 95 7 Sep 19:36 OK —
Customers, dealers and suppliers into the Platform 73 7 Sep 18:36 OK, no change —
Financial summary into the Platform 12 7 Sep 18:36 OK —
Works order creation into HARMONiQ 0 7 Sep 19:31 OK —
Component consumption into HARMONiQ 0 7 Sep 19:31 OK —
Finished goods receipt into HARMONiQ 0 7 Sep 19:03 OK —
Purchase requisitions into HARMONiQ 0 7 Sep 19:03 OK —
Build completion dates on order lines into HARMONiQ 0 7 Sep 19:31 OK —

HubSpot

HubSpot
Private app token, REST API
EntityDirectionRecordsLast runStatusThis session
Companies into the Platform 55 7 Sep 19:29 OK, no change —
Contacts into the Platform 117 7 Sep 19:29 OK —
Deals and deal stages into the Platform 625 7 Sep 19:29 OK —
Marketing campaign performance into the Platform 10 7 Sep 18:29 OK —
Form submissions and enquiries into the Platform 1,230 7 Sep 19:29 OK —
Deal stage on order confirmation into HubSpot 0 7 Sep 18:52 OK —
Build completion date onto deal into HubSpot 0 7 Sep 18:52 OK —
Serial and despatch date onto contact into HubSpot 0 7 Sep 18:04 OK —

Write-backs made in this session

0
WhenSystemEntityReferenceDetail
Nothing has been written back yet in this session. Advance a card on the shop floor, raise a requisition, or confirm a quoted order and every write will be listed here with a timestamp.

Data held by the Platform

Compiled dataset — no D1 binding on this deployment
TableIn D1In the workerAgrees
product — 120 no binding
component — 452 no binding
sub_assembly_bom — 970 no binding
customer — 55 no binding
supplier — 18 no binding
sales_order — 95 no binding
build_order — 170 no binding
build_sub_assembly — 1,164 no binding
purchase_order — 26 no binding
machine — 755 no binding
email_thread — 47 no binding
hubspot_deal — 625 no binding
enquiry — 1,230 no binding

The reference dataset is written to D1 by seed.sql, which is generated from the same source the worker compiles in, and scripts/verify.ts proves the two agree before a build is released. Rows that differ are the ones this session has changed.

Activity in this session

0
Nothing has been changed in this session.

Walkthrough

Everything a walkthrough does — a card advanced, a requisition raised, an order confirmed, an enquiry submitted from the portal — is written to Cloudflare D1 and laid over the seeded baseline. Resetting puts it back exactly as it started, and the underlying dataset is never touched.

Nothing to reset.
Demo date
8 Sep 2026
Walkthrough store
Worker isolate memory, no D1 binding
HARMONiQ read cadence
Stock and orders every 5 minutes, master data hourly
HARMONiQ write cadence
On the event
HubSpot read cadence
Deals and contacts every 15 minutes, campaigns hourly
HubSpot write cadence
On the event