make
/make
Triggers and manages Make (Integromat) scenarios via MCP integration. Use when running scenarios, inspecting run history, or debugging failed Make automations.
- Author
- poly-gents ↗
- Repository
- syncolab-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 12.08.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.08.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Triggers and manages Make (Integromat) scenarios via MCP integration. Use when running scenarios, inspecting run history, or debugging failed Make automations.
Original author description
Triggers and manages Make (Integromat) scenarios via MCP integration. Use when running scenarios, inspecting run history, or debugging failed Make automations.
How it works
- Purpose
- When to Use
- When NOT to Use
- Expected Outcome
- Inputs to Gather
- Workflow
- Domain guidance
- Tool Availability Rules
- Review / Decision / Execution Criteria
- Output Format
SKILL.md preview
--- name: make description: Triggers and manages Make (Integromat) scenarios via MCP integration. Use when running scenarios, inspecting run history, or debugging failed Make automations. --- # Make Automation ## Purpose List, trigger, and debug Make scenarios through MCP tools, reporting real run status and module errors—not assumed success. ## When to Use - User references Make scenarios, modules, connections, or runs. - One-off or scheduled scenario execution and verification. - Debugging failed scenario runs (mapping, API, quota). - Updating scenario configuration when write tools are available. ## When NOT to Use - n8n or Zapier → **n8n**, **zapier**. - Custom code integrations outside Make → implementation skills. ## Expected Outcome - Scenario ID/name and run status with error module if failed. - Input/output bundle highlights from tool responses. - Explicit inability to reach Make org when disconnected. ## Inputs to Gather - Scenario name/ID and organization/team if multi-tenant. - Required input fields for manual run. - Run ID or timestamp for failures. - Production vs test scenario distinction. ## Workflow 1. Search/list scenarios when ID unknown. 2. Get scenario structure (trigger, critical modules). 3. Run with validated input; record run ID. 4. Inspect run details until complete/failed. 5. Summarize errors with module name and mapped fields. 6. Confirm before enabling schedules or high-volume scenarios. ## Domain guidance 1. **Scenario identity** — resolve ID before run or update. 2. **Run history** — use latest failed run for debugging. 3. **Connections** — auth errors often need connection renewal, not code changes. 4. **Data mapping** — verify JSON/path mappings between modules on failures. 5. **MCP-only APIs** — do not invent Make HTTP endpoints. ### Examples **User:** "Run the CRM sync scenario with accountId 42." → Locate scenario, execute with input, return run status and record counts if present. **User:** "Scenario failed at midnight—what broke?" → Pull failed run, identify module, error text, and input bundle snippet (redacted). ## Tool Availability Rules | Access | Behavior | |--------|----------| | Full tool access | Run scenarios and approved edits. | | Read-only | Inspect scenarios/runs; plan changes separately. | | No integration | Do not fabricate run results. | ### Related tool sets - `make` - `custom-apis` ## Review / Decision / Execution Criteria - Always report run ID and final status. - Confirm scenarios that write to production CRMs/ERP without dry-run. ## Output Format 1. Scenario and action. 2. Run ID and status. 3. Error module or output summary. 4. Blockers. 5. Next steps. ## Quality Bar - No spreadsheet/A1 content—Make is scenario automation only. ## Safety and Boundaries - Redact PII from bundles in summaries. - Confirm high-volume or billing-related scenario triggers. ## Escalation / Dispatch Rules - Related iPaaS tools → **n8n**, **zapier**, **run-automation**. ## References - `skills/old_skills.json` (`make`) — legacy catalog (Sheets boilerplate removed). - `skills/skill.instruction.md`, `skills/meta.instructions.md`
Files in this package (2)
- SKILL.md 3 KB
- meta.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · poly-gents/syncolab-skills | 100 | Apache-2.0 |
| ericrisco/rsc-harness | 100 | MIT |
| matheussilvano/videomaker | 100 | MIT |
| jabbarlee/open-papertrail | 100 | MIT |
| Mahdi-Ai-Agent/synapse-os | 100 | MIT |
| OutlineDriven/outline-driven-development | 100 | Apache-2.0 |
| mohitmishra786/low-level-dev-skills | 100 | MIT |
| gosuda/dalcom-skills | 95 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version f2b5bb1c5e7b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100make-com
Make.com (formerly Integromat) is a visual automation platform that connects apps into scenarios of modules, routers, iterators and aggregators, without code. Use when the user wants to build or debug a Make scenario, map data between modules, call an API with the HTTP module,… - 100make-webhooks
Receive and authenticate requests sent by Make (formerly Integromat) scenarios through the HTTP > Make a request module. Use when building an endpoint that a Make scenario calls, securing it with an API key keychain header, debugging 401s from Make, or routing scenario payloads… - 100zapier-make-integrations
Best practices for building robust integrations, CLI apps, and complex scenarios on Zapier and Make (Integromat). Use when building custom Zapier CLI triggers/actions, Make custom apps/modules (JSON I/O, IMLS), webhooks, data transformation, rate limiting, and failure handling. - 100make-scenario-operations
Use when running a scenario, switching it on or off, reviewing or debugging executions, or investigating a webhook that receives nothing. Not for creating, editing or explaining a scenario. - 100n8n
Triggers and manages n8n workflows via MCP integration. Use when listing workflows, running executions, inspecting failures, or updating automation definitions in n8n. - 100make-scenarios
Analyze a plan or codebase to generate scenarios in "Actor wants to..." format from a stated perspective. Use when user says "make scenarios", "generate scenarios", "jeopardy requirements", or wants to identify extension points and use cases.