gidzman/companylens-hubspot-middleware — explained in plain English
Analysis updated 2026-05-18
Receive and verify HubSpot webhook events with cryptographic signature checking before trusting them.
Keep company records synced between HubSpot and an internal backend system.
Normalize field values, such as revenue figures, into the exact format HubSpot expects.
Search for or create company records in HubSpot through a small REST API layer.
| gidzman/companylens-hubspot-middleware | 00kaku/gallery-slider-block | 0xkinno/vellum | |
|---|---|---|---|
| Stars | 0 | — | 0 |
| Language | JavaScript | JavaScript | JavaScript |
| Last pushed | — | 2021-05-19 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | moderate | easy | hard |
| Complexity | 2/5 | 2/5 | 4/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a HubSpot API client secret and app configuration before the webhook signature check can work.
CompanyLens is a small backend service built with Node.js and Express that connects a company's internal systems to HubSpot, a popular customer relationship management tool used by sales and marketing teams. Its job is to keep company data in sync between HubSpot and whatever other systems a business runs, instead of relying on a generic third party connector that may be slow or limited. The main feature is handling incoming webhook events from HubSpot, which are messages HubSpot sends automatically whenever something changes, such as a company record being updated. Before trusting one of these messages, CompanyLens checks a cryptographic signature attached to the request. It reads the HubSpot signature header, recalculates the expected signature locally using a private secret key and the standard HMAC-SHA256 method, and compares the two. If they do not match, the incoming request is rejected immediately, which protects against fake or tampered webhook calls. The project also handles some data cleanup work, such as adjusting field values so they fit the exact format HubSpot expects for a given property, like a company's annual revenue field. It includes basic logging so a developer can see what happened when something goes wrong. Under the hood, CompanyLens uses the official HubSpot API client library to talk to HubSpot, and Node's built in cryptography tools to do the signature checking, so no extra security library is required. The code is organized into a small number of folders: configuration and setup, route handlers for company search and creation plus the webhook receiver, and a service layer that wraps the HubSpot SDK calls. This is a fairly small, single purpose project rather than a full platform. It does not describe a user interface, a database of its own, or support for CRM systems other than HubSpot. There is no license file or license type mentioned in the material provided, so its usage terms are unclear.
A Node.js middleware service that securely syncs company data with HubSpot CRM, verifying every incoming webhook with a cryptographic signature check.
Mainly JavaScript. The stack also includes Node.js, Express, HubSpot API.
No license file or license type is mentioned in the project, so it is unclear what uses are permitted.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.