Make.com CRM Automation

Why CRM Automation in Make.com

Make.com is well-suited for CRM automation because:

• Bidirectional sync: Move data from any source into your CRM, and from your CRM to other tools
• Visual logic: The Router module makes conditional CRM routing (different actions for different lead types) easy to build
• Error handling: Failed CRM updates are caught, retried, and logged — not silently dropped
• Real-time webhooks: Respond to CRM events instantly via webhook triggers

The most common CRM for Make.com automation is HubSpot, which has excellent Make.com modules. Salesforce is also well-supported.

Lead Enrichment Automation

Scenario: Enrich every new HubSpot contact automatically

1. HubSpot trigger: Watch new contacts (instant trigger via webhook)
2. HTTP Request to Apollo.io: Pass the contact's email domain — get company name, size, industry, tech stack, LinkedIn
3. HTTP Request to Claude API: "Given this company info, score the fit with our ICP [describe ICP]. Return JSON: {'score': 0-100, 'reasoning': '...', 'recommended_action': 'call|nurture|disqualify'}"
4. Router: Branch by recommended_action

- Call → Create a HubSpot task for the assigned rep: "High-priority lead: [name] at [company]. Score: [score]. Reason: [reasoning]. Call today." - Nurture → Enroll in HubSpot nurture sequence - Disqualify → Set contact status to "Not a Fit," add note with reasoning

1. HubSpot Update Contact: Write all enrichment data to custom properties

Every new contact arrives enriched, scored, and routed before any human sees it.

Form Submission to CRM

Scenario: Website form → HubSpot contact + task + Slack alert

1. Webhook trigger: Your website form posts to a Make.com webhook URL on submission
2. HubSpot Search Contact: Check if the contact already exists (by email)
3. Router: Exists vs. new

- New contact branch: - HubSpot Create Contact (with form field data) - HubSpot Create Task: "Follow up with new lead within 24 hours" - Slack message to #sales-leads: formatted card with contact details and form answers - Existing contact branch: - HubSpot Update Contact (update last activity, note the form submission) - HubSpot Create Note: "Re-engaged via [form name] on [date]" - Slack message to #sales-leads: "[Contact name] re-engaged via [form name]"

No form submission falls through without a follow-up task and team notification.

Meeting to CRM Note

Scenario: Post-meeting summary → HubSpot

1. Trigger: Webhook from meeting transcription tool (Otter.ai, Fireflies, Gong) — fires when a meeting transcript is ready
2. HTTP Request to Claude: "Summarise this meeting transcript as a CRM note. Include: (1) attendees, (2) what was discussed, (3) pain points mentioned, (4) commitments made, (5) next steps. Format as a structured note."
3. HubSpot Search Contact: Find the contact by email (from meeting attendee list)
4. HubSpot Create Note: Write the summary to the contact record
5. HubSpot Create Tasks: For each next step identified by Claude, create a HubSpot task with due date
6. HubSpot Update Deal: Move deal stage if warranted (Claude identifies "they want a proposal" → move to Proposal Requested)

Reps leave every meeting with the CRM already updated.

Pipeline Health Monitoring

Scenario: Weekly pipeline health report

1. Schedule trigger: Every Monday at 8 AM
2. HubSpot Search Deals: All open deals (multiple HubSpot Search modules with different filters)
3. For each deal (Iterator):

- Calculate days since last activity - Calculate days until close date - Identify risk signals: no activity 14+ days, close date passed, no meeting in 30 days

1. Aggregator: Collect all at-risk deals
2. Claude: "Given these at-risk deals, what's the most important thing for a sales manager to know this week? Give specific recommendations for each deal."
3. Slack message: Weekly pipeline digest to sales manager channel with Claude's analysis

Deal Stage Automation

Scenario: Automate deal stage progression based on activity

1. HubSpot trigger: Deal property updated
2. Router: Branch by which property was updated

- Proposal sent → Move to "Proposal Sent" stage; create task "Follow up in 3 days" - Contract signed → Move to "Closed Won"; trigger onboarding sequence; notify success channel - Meeting booked → Move from "Connected" to "Qualified" if currently there

1. HubSpot Update Deal: Apply stage change
2. HubSpot Create Tasks: Create appropriate next-step tasks

Recommended Tools

• Make.com — Scenario automation platform
• HubSpot — CRM with excellent Make.com integration
• Salesforce — Enterprise CRM, also well-supported
• Claude API — Meeting summarisation, lead scoring
• Apollo.io — Lead enrichment data
• Slack — Team notifications and sales alerts