DataLatte
Make.com AI Agent Workflow for Local Business: Complete Blueprint (2026)
AI Automation

Make.com AI Agent Workflow for Local Business: Complete Blueprint (2026)

June 13, 2026·Nataliia· 12 min read All posts
Make.com (formerly Integromat) is one of the most powerful no-code automation tools available to small businesses. When you connect it to an AI model, it stops being just an automation platform and becomes an AI agent — a system that reads context, makes decisions, and takes personalized action without human input.
This article walks through a specific, working workflow: a lead follow-up agent that triggers when someone fills out your contact form, qualifies the lead, generates a personalized reply using AI, sends the email, and notifies you only if it can't handle the lead itself.

What This Workflow Does

New form submission (Typeform / Gravity Forms / any webhook)
      ↓
  Extract: name, service interest, budget, location
      ↓
  AI qualification (is this a good fit?)
      ↓
  Good fit → Generate personalized email → Send via Resend → Log to Google Sheets
  Poor fit → Send polite "not right for us" email → Log reason
      ↓
  Notify owner via Slack/email only if lead is high-value or needs human input
This workflow handles 80% of inbound leads fully automatically. You only get notified when a lead is genuinely worth your personal attention.

Module-by-Module Setup

Module 1: Webhook Trigger

Add a Webhooks → Custom webhook module. This is the entry point — any form submission, Typeform response, or manual API call will trigger the workflow.
Get the webhook URL and paste it into your form's "webhook" or "notification" settings.
The webhook receives JSON like this:
{
  "name": "Sarah Johnson",
  "email": "sarah@coffeeshop.com",
  "phone": "+15551234567",
  "business_type": "Coffee shop",
  "service_interest": "Google Ads + Local SEO",
  "monthly_budget": "$500-1000",
  "city": "Austin, TX",
  "message": "We opened 3 months ago and need help getting found on Google Maps"
}

Module 2: OpenAI / Groq — Lead Qualification

Add an HTTP → Make an API Key Request module (use this for Groq — it's cheaper and faster than OpenAI for classification tasks).
URL: https://api.groq.com/openai/v1/chat/completions
Method: POST
Headers:
Authorization: Bearer {{GROQ_API_KEY}}
Content-Type: application/json
Body (raw JSON):
{
  "model": "llama-3.3-70b-versatile",
  "messages": [
    {
      "role": "system",
      "content": "You are a lead qualification assistant for a local marketing agency. Classify leads as GOOD_FIT, MAYBE, or NOT_FIT. Reply with only a JSON object: {\"classification\": \"GOOD_FIT\", \"reason\": \"one sentence\", \"priority\": \"high/medium/low\"}"
    },
    {
      "role": "user",
      "content": "Lead details:\nName: {{1.name}}\nBusiness: {{1.business_type}}\nService interest: {{1.service_interest}}\nBudget: {{1.monthly_budget}}\nMessage: {{1.message}}\n\nGOOD_FIT: local business, budget $300+/month, clear need\nNOT_FIT: wants free work, huge enterprise, completely wrong service, budget under $200\nMAYBE: everything else"
    }
  ],
  "max_tokens": 100,
  "temperature": 0.2
}
Parse the response: Use a JSON → Parse JSON module on choices[0].message.content.

Module 3: Router — Branch by Classification

Add a Router module with 3 paths:
  • Path A: classification = GOOD_FIT
  • Path B: classification = MAYBE
  • Path C: classification = NOT_FIT

Module 4A: AI Email Generation (Good Fit)

For GOOD_FIT leads, generate a personalized outreach email.
Add another HTTP module calling Groq:
{
  "model": "llama-3.3-70b-versatile",
  "messages": [
    {
      "role": "system",
      "content": "You write personalized, conversational business emails. Sound like a real person, not a marketing robot. No buzzwords. Under 200 words. Sign off as Nataliia from DataLatte."
    },
    {
      "role": "user", 
      "content": "Write a reply to this inquiry:\n\nFrom: {{1.name}} ({{1.business_type}} in {{1.city}})\nInterested in: {{1.service_interest}}\nBudget: {{1.monthly_budget}}\nTheir message: {{1.message}}\n\nMake it:\n- Acknowledge their specific situation (mention their business type and city)\n- Reference 1 specific thing from their message\n- Suggest a quick 20-min call to see if we're the right fit\n- Include a Calendly link: https://calendly.com/datalatte/discovery\n- Warm but concise"
    }
  ],
  "max_tokens": 300,
  "temperature": 0.7
}

Module 4B: Template Email (Maybe / Not Fit)

For MAYBE leads, use a softer template. For NOT_FIT, a polite decline.
You can hardcode these or use light AI generation. A simple template for NOT_FIT:
Hi {{1.name}},

Thanks for reaching out to DataLatte! After reviewing your inquiry, I don't think we're the best fit for what you need right now — our services are focused on [specific gap in their request].

I'd recommend checking out [alternative resource].

Wishing you the best with {{1.business_type}}!

Nataliia
DataLatte.pro

Module 5: Send Email via Resend

Add an HTTP → Make an API Request module:
URL: https://api.resend.com/emails
Headers:
Authorization: Bearer {{RESEND_API_KEY}}
Content-Type: application/json
Body:
{
  "from": "Nataliia at DataLatte <hello@datalatte.pro>",
  "to": ["{{1.email}}"],
  "subject": "Re: Your inquiry about {{1.service_interest}}",
  "html": "<p>{{4A.choices[0].message.content}}</p>"
}

Module 6: Log to Google Sheets

Add a Google Sheets → Add a Row module. Log:
  • Timestamp
  • Name, email, business type, city
  • Service interest, budget
  • Classification + reason
  • Email sent (yes/no)
  • Priority level
This gives you a live lead database without any CRM.

Module 7: Slack / Email Notification (High Value Only)

Add a filter: only continue if priority = high. Then send yourself a Slack message or email with the lead summary and a link to their row in Google Sheets.
This is the key design principle: you only hear about leads worth acting on immediately. Everything else is handled and logged.

Full Workflow JSON (Import into Make.com)

You can import this as a blueprint. Create a new scenario in Make.com → click the three dots → Import Blueprint → paste this JSON:
{
  "name": "Lead Follow-Up AI Agent",
  "flow": [
    {
      "id": 1,
      "module": "gateway:CustomWebHook",
      "version": 1,
      "metadata": {
        "designer": {"x": 0, "y": 0}
      }
    },
    {
      "id": 2,
      "module": "http:ActionSendData",
      "version": 3,
      "parameters": {
        "handleErrors": false,
        "useNewZLibDecompression": true
      },
      "mapper": {
        "url": "https://api.groq.com/openai/v1/chat/completions",
        "method": "post",
        "headers": [
          {"name": "Authorization", "value": "Bearer {{GROQ_API_KEY}}"},
          {"name": "Content-Type", "value": "application/json"}
        ],
        "bodyType": "raw",
        "contentType": "application/json",
        "body": "{\"model\":\"llama-3.3-70b-versatile\",\"messages\":[{\"role\":\"user\",\"content\":\"Classify this lead as GOOD_FIT, MAYBE, or NOT_FIT. Reply with JSON only: {classification, reason, priority}. Lead: {{1.name}}, {{1.business_type}}, Budget: {{1.monthly_budget}}\"}],\"max_tokens\":100}"
      }
    },
    {
      "id": 3,
      "module": "json:ParseJSON",
      "mapper": {
        "string": "{{2.body.choices[].message.content}}"
      }
    }
  ],
  "metadata": {
    "version": 1,
    "scenario": {"roundtrips": 1, "maxErrors": 3, "autoCommit": true}
  }
}
Replace {{GROQ_API_KEY}} with your actual key stored in Make.com's data stores or as a scenario variable.

Real Results: What This Workflow Replaces

Before building this workflow, a typical local marketing consultant spends:
  • 30–60 min/day replying to inbound inquiries
  • 10–15 min qualifying each lead manually
  • Inconsistent follow-up timing (some leads wait 4+ hours)
After: the system responds to 80% of leads within 2 minutes. You check the Google Sheets log every morning and the Slack notification for high-value leads. The only manual work left is the discovery calls.
For a solo consultant handling 10–20 leads/week, this saves 3–5 hours per week and increases reply-rate conversion by 20–30% because of faster response time.

Frequently Asked Questions

Q: Do I need a paid Make.com plan for this workflow?
The free Make.com plan includes 1,000 operations/month. Each lead that runs through this workflow uses about 6–8 operations. At 1,000 operations, that's 125–166 leads per month on the free plan. If you're getting more than that, upgrade to the Core plan ($9/month). Groq is free up to 14,400 API requests/day on LLaMA 3.3. Resend is free up to 3,000 emails/month. The total cost to run this workflow for most local businesses: under $10/month.
Q: What form tools work as the webhook trigger?
Any tool that supports webhooks: Typeform, Tally (free), Gravity Forms, WPForms, JotForm, Fillout, or a simple HTML form with a fetch() call. Make.com's webhook URL accepts any POST request with JSON or form-encoded data. If your form tool doesn't support webhooks directly, use Zapier's webhook step as a bridge, or switch to Tally (which has native Make.com integration and is free).
Q: Can I add a follow-up sequence — like if they don't respond in 3 days?
Yes. Add a delay module after logging to Google Sheets. Set it to 72 hours. Then check Google Sheets to see if a "replied" column is still empty. If so, trigger a second follow-up email. This requires Make.com to run on a schedule (add a second scenario triggered by the Google Sheets log). It's more advanced but very doable with Make.com's native scheduling.
Q: How do I handle leads that come from different sources (Instagram DMs, email, web form)?
Create separate webhook triggers for each source, all routing into the same core workflow. Or use Make.com's Gmail module to watch your inbox for new inquiry emails, parse the content with AI, and route them through the same qualification logic. The core AI qualification step works regardless of the lead source.
Q: What if the AI generates a bad email and sends it before I can review it?
Add a manual approval step for high-value leads. Instead of sending immediately, log the AI-generated draft to a Google Sheet and send yourself a notification. Only after you approve (click a link that updates the sheet) does the system actually send the email. You can build this with a Make.com scenario triggered by the sheet update. It adds a manual step but gives you a human review gate for important leads.

Want More Local Customers?
Nataliia at DataLatte runs data-driven local marketing campaigns for local businesses — coffee shops, salons, pet groomers, and fitness studios. Book a free 30-minute strategy call or explore Google Ads management.

Free for local businesses

Want this applied to your business?

I'll review your Google presence, local SEO, and ad accounts — and send you a specific action plan within 48 hours. No pitch, no pressure.

Want hands-on help?

See how DataLatte handles AI Agents & Automation for local businesses.

Learn more
Nataliia — local marketing expert
Nataliia

Local marketing strategist with 10+ years at global agencies — OMD, Dentsu, GroupM, and BBDO. Now helping small businesses get the same data-driven edge. Based in Europe, working with clients in the US, UK, Australia, and beyond.

About Nataliia

Want this applied to your business?

Let's review your current marketing setup together — free, no obligations.

Get Your Free Marketing Audit