make-scenario-building
Make Scenario Building
This skill guides building a scenario in Make. A scenario is an automated workflow composed of modules connected together. Before building anything, Phase 1 below MUST be completed.
Phase 1: Understand the Business Need & Identify Modules
Phase 1 has three steps. Do not skip or rush any of them.
Step 1: Clarify the Business Use Case
The first job is to understand exactly what the user wants to automate. Use an adaptive interview approach:
- Start conversational. Ask 1-2 focused questions about what they want to achieve:
- What task or process do they want to automate?
- Which systems or services are involved?
More from integromat/make-skills
make-mcp-reference
This skill should be used when the user asks about "Make MCP server", "Make MCP tools", "MCP token", "Make OAuth", "scenario as tool", "MCP scopes", "Make API access", "connect Make to Claude", "scenario not appearing", "MCP timeout", "MCP connection refused", or discusses configuring, troubleshooting, or understanding the Make.com MCP server integration. Provides technical reference for connection methods, scopes, access control, and troubleshooting.
40make-module-configuring
This skill should be used when configuring Make module parameters, assigning connections, mapping data between modules, setting up webhooks or data stores in modules, working with IML expressions, handling keys, or defining data structures for module inputs/outputs. Covers the practical HOW of module configuration — complementary to make-scenario-building which covers WHICH modules to use and WHY.
40make-api-shell-connection-workflow
This skill should be used when Claude needs to build or reuse a reusable Make API-call shell by discovering the correct app-specific Make an API Call module, resolving or requesting the right connection, explicitly setting the scenario interface, running the scenario, and using that shell as the retrieval transport for email, CRM, tickets, and similar SaaS systems.
27