Feature Requests

We're introducing tool templates to the Tools Canvas — making it easier to reuse and share common tool stacks across workspaces. Here's how it works: Browse templates by clicking the new template icon on the Tools Canvas. You'll find Puzzle-curated templates under Explore, and your own saved templates under My Templates. Save your own template using the "Save as Template" option in a tool group's sidebar — similar to how workflow section templates work today. Use, edit, or delete your saved templates directly from the template library. Templates carry over tool names, layout, and notes — without any cost or billing information.

We're introducing tab-level permissions for the Workflows canvas, giving Enterprise workspaces more control over who can see specific tabs. By default, all tabs are public within a workspace — but owners and admins can switch any tab to private and control exactly which workspace members have access. Private tabs will display a lock icon so it's clear they're restricted. Members without access simply won't see the tab. This feature is available on the Enterprise plan. Users on other plans will see the option but will be prompted to upgrade to access it.

We're adding Shared View management to MCP and Nova. You'll be able to ask Nova to create a new Shared View, add or remove workflow sections, people, teams, and tool groups — all through a simple conversation, without having to configure it manually in the app.

We're adding support for .docx file uploads in Puzzle. You'll be able to upload Word documents when using Nova, as well as during the onboarding process for mapping your processes, org chart, and tools — making it easier to get your existing documentation into Puzzle without having to copy and paste.

🔄 Current Situation Right now, Puzzle is a useful top-down collaborative mapping tool. However, it relies entirely on human memory. Users often suffer from the "cold start" problem: they stare at a blank canvas because their most repetitive daily tasks have become invisible, automated habits. They don't know what to map. 💡 Feature Request Description Introduce a lightweight Puzzle Browser Extension that acts as a passive "Workflow Scout", bringing a MemoryLane-style approach directly into the browser. It analyzes browser tab sequences, form inputs, and copy-paste patterns across SaaS apps. When it detects a repetitive sequence (e.g., repeating a 5-step process between HubSpot, Gmail, and a internal tool), it keeps a pattern history and optionally sends a push notification: "We noticed you did this sequence 3 times today. Click here to auto-generate a Puzzle blueprint." This transforms Puzzle from a reactive documentation tool into an active Process Discovery Engine . 🛠️ Implementation Suggestion To avoid the security, privacy, and development nightmares of a full desktop app (like task-mining competitors do), start with a Chromium Extension . Cross-Platform Support: A browser extension runs out-of-the-box across Windows, macOS, and Linux. The extension monitors URLs and DOM interactions locally. It uses a local script to cluster repetitive patterns. With one click, the user sends the raw text steps to Puzzle's AI to instantly generate the visual workflow on their dashboard. 🔑 Feasibility (BYOK) To reduce AI infrastructure and token costs for Puzzle, this feature can run on a BYOK (Bring Your Own Key) model. Users plug in their OpenAI-Compatible provider (BaseURL setup + API key) Puzzle incurs zero AI compute costs for the background processing and text-to-map generation. This keeps the feature highly scalable, private, and predictable for your team to maintain. 📚 References Examples of services using background task-mining to feed process intelligence: MemoryLane UiPath Task Mining HASH AI (Privacy-Preserving Process Mining)

Users will be able to integrate with Go High Level to sync their Forms, Workflows, and Chatflows within Puzzle's workflow canvas.

I would like the ability to resize individual step boxes within the application. Currently, only sections can be resized, which limits customization. Having the option to adjust the size of each step box would enhance flexibility and allow for better organization of content.

The current setup requires guessing which WRITE commands to use with Hermes, unlike Claude where you can toggle read/write options per command. A generic pathway for all MCP-compatible tools would streamline this process and prevent trial-and-error issues.

Need to work hermes agent into the loop!

Users will be able to import their tech stack via .csv to quickly add the related tools to the tool canvas.