stackstrategiststackstrategist
SalesAutomationCross-stack blueprint

Automating HubSpot + Make.com Stack Workflows with Make.com

These tools sit in different operational verticals. Instead of a feature matrix, this page maps a production-grade integration path: trigger → Make.com transform → downstream action, with explicit auth at each API node.

Connection endpointshubspot · triggermake · middlewaremake · action
  1. 1

    The Trigger Event

    HubSpot

    When HubSpot emits ‘Deal Stage Changed’ via its Webhook Listener, Make.com opens the scenario run. Native trigger catalog for this node:

    • Deal Stage Changed
    • Contact Created
    • Form Submission
    hubspot → make.com payloadwebhook / json
    {
  "source": "hubspot",
  "event": "Deal Stage Changed",
  "listener": "webhook",
  "category": "Sales",
  "auth": "OAuth 2.0"
}

    Alternate entry points: Contact Created · Form Submission

  2. 2

    The Middleware Transformation

    Make.com

    Make.com captures the raw webhook payload, applies router filters on data state (status, adjudication flags, or CRM field presence), then maps JSON objects into the destination schema using native module mappers—no custom ETL service required.

    make.com transform mapwebhook / json
    {
  "middleware": "make.com",
  "filter": { "status": "actionable" },
  "map": {
    "from": "hubspot.Deal Stage Changed",
    "to": "make.Run Scenario"
  },
  "nodes": ["hubspot", "make", "make"]
}
  3. 3

    The Downstream Action

    Make.com

    Make.com instantly fires ‘Run Scenario’ so the receiving system reflects the upstream event without manual handoff.

    • Run Scenario
    • Create Data Store Record
    • HTTP Request

    Optional follow-on actions: Create Data Store Record · HTTP Request

View Make.comHubSpot reviewMake.com review