Sponsor Suno AI Music arrow_forward
Plugin

Make Scenario Builder

Create Make.com (Integromat) scenarios with AI assistance - visual automation design

Type
Plugin
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026
Version
1.15.0
Author
Claude Code Plugin Hub

What Make Scenario Builder is

Make Scenario Builder is a plugin published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A plugin is a package that bundles skills, slash commands, subagents, hooks, and MCP connectors so they install together. Plugins are plain files with a manifest at .claude-plugin/plugin.json, and they work in both Claude Code and Claude Cowork.

Installing Make Scenario Builder adds everything it ships in one step. Connectors inside a plugin still need to be connected separately, and hooks and subagents only run in Cowork and Claude Code, not in regular chat.

How to install Make Scenario Builder

Claude Code

  1. Add the repository as a plugin marketplace: claude plugin marketplace add jeremylongshore/tons-of-skills-marketplace
  2. Install the plugin: claude plugin install make-scenario-builder@<marketplace-name>, using the marketplace name from the repository's .claude-plugin/marketplace.json.
  3. Restart the session if the new skills or commands don't appear straight away.

Claude Cowork

  1. Open Customize → Plugins and choose Add marketplace.
  2. Enter jeremylongshore/tons-of-skills-marketplace (the owner/repo shorthand works for GitHub).
  3. Find Make Scenario Builder in the list, click Install, then connect any connectors it needs from its Connectors tab.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/ai-agency/make-scenario-builder/.claude-plugin/plugin.json, shared under the repository's MIT license. Read the full file on GitHub.

Create visual Make.com automation scenarios with AI assistance - perfect for no-code automation.

Why Make.com?

Make.com (formerly Integromat) is a powerful visual automation platform:

  • Visual Design - See your entire workflow at a glance
  • 1000+ Integrations - Connect virtually any app
  • No-Code - Build complex automations without coding
  • Powerful Features - Routers, filters, error handlers
  • Affordable - More cost-effective than Zapier
  • Scalable - Handle complex multi-step workflows
  • ️ Built-in Error Handling - Visual error routes

FREE Alternative: Use n8n + Ollama (Self-Hosted)

Want the same power without monthly costs? Use n8n (self-hosted) + Ollama (local LLM) for $0/month.

Quick Comparison

Savings: $468-1,068/year (enough to buy new hardware!)

Why n8n + Ollama?

n8n (Self-Hosted Automation):

  • Visual workflow builder (same as Make.com)
  • 400+ integrations (vs Make's 1000+, but covers 90% of use cases)
  • Advanced error handling
  • Self-hosted = unlimited operations
  • Open-source = community support

Ollama (Local LLM):

  • Runs Llama 3.2, Mistral, CodeLlama locally
  • No API keys required
  • Privacy-first (data never leaves your machine)
  • Free forever

Setup Guide

1. Install n8n (Docker)

# Create docker-compose.yml
cat > docker-compose.yml <<'EOF'
version: '3'
services:
  n8n:
    image: n8nio/n8n
    ports:
      - "5678:5678"
    environment:
      - N8N_BASIC_AUTH_ACTIVE=true
      - N8N_BASIC_AUTH_USER=admin
      - N8N_BASIC_AUTH_PASSWORD=changeme
    volumes:
      - ~/.n8n:/home/node/.n8n
EOF

# Start n8n
docker-compose up -d
…

2. Install Ollama

# macOS
brew install ollama
brew services start ollama

# Linux
curl -fsSL https://ollama.com/install.sh | sh

# Pull AI model (4GB download)
ollama pull llama3.2

See ollama-local-ai plugin for detailed setup.

3. Connect Ollama to n8n

In n8n, use the HTTP Request node:

{
  "method": "POST",
  "url": "http://localhost:11434/api/generate",
  "body": {
    "model": "llama3.2",
    "prompt": "{{ $json.input }}",
    "stream": false
  }
}

Migration Examples

Before (Make.com + OpenAI)

Cost: $9/mo + $30/mo = $39/mo

Trigger: Gmail New Email
↓
Action: OpenAI Chat Completion ($0.002/request)
↓
Action: Gmail Send Reply
↓
Action: Google Sheets Add Row

After (n8n + Ollama)

Cost: $0/mo + $0/mo = $0/mo

Trigger: Gmail New Email (n8n)
↓
HTTP Request: Ollama Chat (localhost:11434)
↓
Action: Gmail Send Reply (n8n)
↓
Action: Google Sheets Add Row (n8n)

Same functionality, zero cost.

Real Use Case: AI Email Assistant

Make.com + OpenAI Version

  • Make.com Core: $9/mo
  • OpenAI API: ~$30/mo (1000 emails)
  • Total: $39/mo

n8n + Ollama Version

// n8n HTTP Request Node
{
  "method": "POST",
  "url": "http://localhost:11434/api/generate",
  "body": {
    "model": "llama3.2",
    "prompt": "Reply professionally to: {{ $json.emailBody }}",
    "stream": false
  }
}
  • n8n (self-hosted): $0
  • Ollama (local): $0
  • Total: $0/mo

Same AI quality, $468/year saved.

n8n Workflow Templates

Available in n8n-workflow-designer plugin:

  • AI email automation
  • Lead scoring & routing
  • Content distribution
  • Document processing
  • Support ticket triage

Performance Comparison

When to Use Make.com vs n8n

Use Make.com if:

  • You need 1000+ integrations (vs n8n's 400+)
  • You prefer managed hosting (no DevOps)
  • Your team is non-technical
  • Budget allows $39-89/month

Use n8n + Ollama if:

  • You want unlimited operations
  • You need privacy/compliance (HIPAA, GDPR)
  • You have basic Docker skills
  • You want to save $468-1,068/year

Resources

  • n8n Docs: docs.n8n.io
  • Ollama Setup: Use /setup-ollama command from ollama-local-ai plugin
  • n8n Workflows: Install n8n-workflow-designer plugin
  • Migration Guide: n8n vs Make.com

Bottom Line: If you're comfortable with Docker and want to save $468+/year, n8n + Ollama is the superior choice.

Installation

/plugin marketplace add jeremylongshore/claude-code-plugins
/plugin install make-scenario-builder

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Make Scenario Builder?

Make Scenario Builder is a plugin for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Create Make.com (Integromat) scenarios with AI assistance - visual automation design

How do I install Make Scenario Builder in Claude Code?

Add the repository as a plugin marketplace: claude plugin marketplace add jeremylongshore/tons-of-skills-marketplace Install the plugin: claude plugin install make-scenario-builder@<marketplace-name>, using the marketplace name from the repository's .claude-plugin/marketplace.json. Restart the session if the new skills or commands don't appear straight away.

Can I use Make Scenario Builder in Claude Cowork?

Open Customize → Plugins and choose Add marketplace. Enter jeremylongshore/tons-of-skills-marketplace (the owner/repo shorthand works for GitHub). Find Make Scenario Builder in the list, click Install, then connect any connectors it needs from its Connectors tab.

Is Make Scenario Builder safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.