Automating Close CRM + 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.
- 1
The Trigger Event
Close CRMWhen 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
The Middleware Transformation
Make.comMake.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": "make.Run Scenario" }, "nodes": ["close", "make", "make"] } - 3
The Downstream Action
Make.comMake.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
- 4
Security & Authentication Protocol
Connected API nodes authenticate independently. Confirm token scopes and refresh routines before promoting this scenario to production.
- Close CRM
- API Key Pass-through
- Make.com
- OAuth 2.0 / Token Refresh
- Make.com
- OAuth 2.0