🔧
Make+Stompy

Scenarios that remember their story

Build scenarios that remember

The Problem

Make (formerly Integromat) is where visual automation becomes art. Complex scenarios with routers, iterators, aggregators. Data transformations that would take hundreds of lines of code, built in a visual canvas. Your scenarios handle edge cases your competitors don't even know exist.

But complex scenarios are still stateless scenarios.

You've built a masterpiece. Webhooks trigger data flows that branch through routers, iterate through arrays, aggregate results, and hit a dozen APIs. It runs flawlessly. Then it forgets everything and waits for the next trigger. The patterns you discovered in production? The data anomalies that needed special handling? The customer IDs that always cause edge cases? Gone. Every execution starts fresh.

Your support automation processes thousands of tickets. It's learned nothing about which responses work, which customers need escalation, which issues cluster together. The router sends ticket type A down path 1 every time—even though you've manually noticed that ticket type A with keyword X should go to path 2.

Make gives you incredible power to build complex logic. But that logic is frozen. It can't adapt based on what happens at runtime. Each scenario is a sophisticated machine with no memory, a genius with amnesia.

Complex automation deserves to evolve.

How Stompy Helps

Stompy transforms Make scenarios from stateless workflows into learning systems.

Before routers make decisions, pull historical context. Which paths have worked for similar data? What patterns have emerged? Make's visual logic becomes informed by actual execution history.

After scenarios complete, save the outcome. What data came through? How was it routed? What was the result? This builds a corpus of institutional knowledge that lives outside Make but informs everything in Make.

Your scenarios get smarter over time: - **Routing informed by history**: Recall which paths worked for similar inputs before the router decides - **Cross-scenario intelligence**: A customer support scenario learns from the sales scenario about the same customer - **Pattern accumulation**: Spot trends across thousands of executions that individual runs can't see - **Error pattern recognition**: Track which data shapes cause issues and preemptively handle them

Build once, execute many times, learn continuously.

Integration Walkthrough

1

Add memory recall before decisions

Place an HTTP module before routers to pull relevant historical context.

{
"name": "Recall Customer Context",
"module": "http.makeRequest",
"parameters": {
"url": "https://mcp.stompy.ai/sse",
"method": "POST",
"headers": [
{"key": "Authorization", "value": "Bearer {{STOMPY_API_KEY}}"},
{"key": "Content-Type", "value": "application/json"}
],
"body": {
"tool": "context_search",
"params": {
"query": "customer:{{customer_id}} recent interactions",
"limit": 5
}
}
}
}
2

Save outcomes after scenario completion

Add an HTTP module at the end of each path to record what happened.

{
"name": "Save Scenario Outcome",
"module": "http.makeRequest",
"parameters": {
"url": "https://mcp.stompy.ai/sse",
"method": "POST",
"headers": [
{"key": "Authorization", "value": "Bearer {{STOMPY_API_KEY}}"},
{"key": "Content-Type", "value": "application/json"}
],
"body": {
"tool": "lock_context",
"params": {
"topic": "scenario_{{scenario_id}}_{{execution_id}}",
"content": "Customer: {{customer_id}}\nInput type: {{trigger_type}}\nRoute taken: {{router_path}}\nOutcome: {{final_status}}\nTimestamp: {{now}}",
"tags": "make,scenario,{{scenario_name}}"
}
}
}
}
3

Build cross-scenario dashboards

Create a dedicated scenario that analyzes patterns across all your automation.

{
"name": "Weekly Pattern Analysis Scenario",
"trigger": "schedule.weekly",
"modules": [
{
"name": "Search All Scenario Outcomes",
"module": "http.makeRequest",
"parameters": {
"url": "https://mcp.stompy.ai/sse",
"method": "POST",
"body": {
"tool": "context_search",
"params": {
"query": "scenario outcomes last 7 days",
"tags": "make,scenario",
"limit": 100
}
}
}
},
{
"name": "Send to Slack/Email",
"module": "slack.sendMessage",
"parameters": {
"text": "Weekly automation insights: {{pattern_summary}}"
}
}
]
}

What You Get

  • Scenarios that route based on historical patterns, not just current data
  • Cross-scenario intelligence sharing through Stompy's project isolation
  • Semantic search to find similar past executions before making decisions
  • Error pattern detection that prevents issues before they cause failures
  • Execution analytics that reveal optimization opportunities across all scenarios

Ready to give Make a memory?

Join the waitlist and be the first to know when Stompy is ready. Your Make projects will never forget again.