stackstrategiststackstrategist
SalesMarketingCross-stack blueprint

Automating Close CRM + Kit 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 endpointsclose · triggermake · middlewarekit · action
  1. 1

    The Trigger Event

    Close CRM

    When Close CRM emits ‘Lead Created’ via its Webhook Listener, Make.com opens the scenario run. Native trigger catalog for this node:

    • Lead Created
    • Opportunity Status Changed
    • Call Completed
    close → make.com payloadwebhook / json
    {
  "source": "close",
  "event": "Lead Created",
  "listener": "webhook",
  "category": "Sales",
  "auth": "API Key Pass-through"
}

    Alternate entry points: Opportunity Status Changed · Call Completed

  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": "close.Lead Created",
    "to": "kit.Add Tag to Subscriber"
  },
  "nodes": ["close", "make", "kit"]
}
  3. 3

    The Downstream Action

    Kit

    Kit instantly fires ‘Add Tag to Subscriber’ so the receiving system reflects the upstream event without manual handoff.

    • Add Tag to Subscriber
    • Add Subscriber to Sequence
    • Create Purchase

    Optional follow-on actions: Add Subscriber to Sequence · Create Purchase

View Make.comClose CRM reviewKit review