Screen new HubSpot companies against Companies House

Trigger this workflow with a HubSpot webhook whenever a new company is created (the company.creation event). Each time a company record lands, run a KYB (know-your-business) due-diligence check against the UK's official register and write the findings back onto the record and to your team.

First, resolve the registered entity. Take the new company's name and any UK company number already present on the HubSpot record. Run Companies House Advanced Company Search using those inputs to find the matching registered entity. If a company number is already on the record, prefer it and treat the search as confirmation. If Advanced Company Search does not return a single confident match (for example several similarly named companies, or none), do not guess a company number.

Once you have a confident match, pull the full picture from Companies House for that company number: Get Company Profile, List Company Officers, List Persons with Significant Control, and Get Company Insolvency.

Write a short due-diligence summary from what you found. Cover: registration status (active, dissolved, liquidation, etc.), incorporation date, registered office address, SIC codes (nature of business), the directors and officers, the persons with significant control (PSCs), and any insolvency history or open cases.

Write the results back to HubSpot. Use Update Company to set the confirmed company number and registration status on the record, then use Create Note to attach the full due-diligence summary, associated with that company.

Finally, post an alert to the sales or compliance channel with the Slack bot Send a Message. Lead with any red flags: a dissolved or closed status, an active insolvency or liquidation case, or missing PSC data (no persons with significant control listed). Include the company name, the confirmed Companies House number, the status, and a link back to the HubSpot record. If Advanced Company Search did not return a single confident match, do not write a company number to HubSpot and instead flag the ambiguity clearly in the Slack alert so a person can resolve it by hand.