Platform Ideas and Improvements

Before you share your idea, check if the request already exists. If it does, simply upvote it.
For missing apps use App Ideas board.
For missing features in apps, use App Improvement Ideas board.
Easier access to module output data from past scenario executions
When building or editing a scenario, I often need to check the execution history to see exactly what data was returned by specific modules and how that data was formatted. This is especially useful when updating an existing scenario or continuing work on a scenario that depends on real execution data. While it is possible to run a module individually, this can become difficult when the module requires parameters. In those cases, you first need to find or recreate the correct input data, which can take time. Most of the time, it is much easier to inspect a previous execution and look at the actual data that was returned. At the moment, when I am working in the scenario editor, my workflow looks like this: Shift-click the scenario button in the menu to open it in a new tab. Open the scenario again. Go to the History tab. Open the execution I want to inspect. This means I end up with two tabs open just to check the data returned by a module. I have two suggestions that could improve this workflow: Load module metadata or output from a previous execution It would be very useful to right-click a module and have an option such as: “View data from previous execution” or “Refresh metadata from execution” This would allow users to inspect the actual data returned by that module in a past run without leaving the scenario editor. It could also help when configuring mappings or troubleshooting formatting issues. Quick access to scenario history As a simpler improvement, add a button in the scenario editor that opens the scenario history directly in a new tab. This would already remove several steps from the current workflow and make it much faster to inspect previous execution data while actively building a scenario.
0
Feature Request: Floating Module Labels in Scenario Editor
Hey Make team! Here's something that's been bugging me hard as a power user with hundreds of scenarios: The ask Let us slap a short label (≤80 chars) right above each module inside the scenario edit view — kind of like a floating sticky note that lives on the canvas . Why it matters Right now, when I'm navigating across a ton of scenarios, I'm flying blind. I have to "open" each scenario just to figure out what it's doing or why I built it. That's a brutal time sink. Same pain hits with AI Agents — each agent module on the canvas should have a floating tooltip/label so I can quickly grok what role that module plays in the flow without having to click into it. What it should look like A tiny, non-intrusive floating tag that hovers "above" the module tile on the canvas — always visible during edit view, never blocking the module itself. Think of it like a sticky label in a circuit diagram. Max 80 chars, editable on double-click or via the module settings. Bonus — make it searchable These labels shouldn't just live on the canvas. They should be "indexed and searchable from the Scenarios View". So when I'm searching across my workspace, the search engine crawls those module labels too — not just the scenario name. That way I can type something like "invoice webhook" or "GPT classifier" in the search bar and surface the exact scenario that has that module, without having to open anything. This is a game-changer for anyone running a complex automation stack. The payoff Instant clarity when scanning any scenario + a way smarter search experience across the whole workspace. No more guessing games. Huge quality-of-life boost for anyone managing complex automation stacks 🙏 Thanks boys
0
Load More