Webhook recipe · HubSpot

HubSpot ↔ Chromoly: pipeline meets operations.

Q: What HubSpot plan do I need for webhooks?

HubSpot's workflow webhook action - the clean way to push events out - sits in Operations Hub Professional. Without it, the outbound direction still works (Chromoly calling HubSpot's API), and form-notification forwarding can cover simple inbound cases. This page states that plainly because most integration marketing doesn't.

Q: Doesn't Chromoly compete with HubSpot?

Different jobs. HubSpot is the marketing/sales CRM; Chromoly generates the internal operational systems HubSpot doesn't cover - delivery tracking, approvals, client portals. This recipe is for teams keeping HubSpot for pipeline and wanting the operational side connected, not for replacing HubSpot. (If you do want a custom CRM instead, that's the custom-crm use case.)

Q: Which direction should I sync?

One direction with a clear owner beats bidirectional cleverness. Typical: HubSpot owns pre-sale (deals push into Chromoly when won, triggering onboarding), Chromoly owns post-sale and writes key milestones back via the outbound API call. Decide the owner per field and the sync stays sane.

HubSpot is where deals happen; it's rarely where delivery happens. This recipe connects the two: a deal marked won in HubSpot starts the operational machine in Chromoly - onboarding, project setup, invoicing - and key milestones flow back. HubSpot stays your CRM; Chromoly runs what happens after yes.

What people build with it

Won-deal handoff - deal closes in HubSpot → onboarding checklist instantiates, project created, kickoff email drafted for approval.
Operational visibility back - delivery milestones write back to the HubSpot deal via outbound API call, so sales sees status without asking.
Form leads both ways - HubSpot form fills can feed internal routing when the sales team isn't the right owner.

The recipe

In Chromoly, add a webhook trigger: "when a won deal arrives, create the client and start onboarding". Copy the URL.

In HubSpot, add a workflow (trigger: deal stage = won) with a Send webhook action to that URL - this action requires Operations Hub Professional, stated honestly.

Close a test deal. Map company, contact, deal value, and owner to your fields once.

For the return direction, add an outbound step in Chromoly: on milestone completion, call HubSpot’s API to update the deal (a private-app token, stored encrypted). Preview, deploy.

Webhook triggers and their signing secrets are covered in the integrations documentation. Every received request - including rejected ones - appears in the workflow's run history, so the connection is debuggable from day one.

Questions

What HubSpot plan do I need for webhooks?

The workflow webhook action sits in Operations Hub Professional. Without it, the outbound direction (Chromoly calling HubSpot's API) still works, and form-notification forwarding covers simple inbound cases.

Doesn't Chromoly compete with HubSpot?

Different jobs - HubSpot is the marketing/sales CRM; Chromoly generates the operational systems around it. Teams wanting a custom CRM instead should read the custom CRM use case.

Which direction should I sync?

One direction per field, with a clear owner. Typical: HubSpot owns pre-sale, pushes won deals into Chromoly; Chromoly owns delivery, writes milestones back.

Build the system this feeds

Describe it in plain language - the webhook trigger is part of the description. Preview free before anything deploys.

Start free