Feature Requests

We need a debugger environment for workflows. It is extremely expensive to build workflows when we have to run the entire process for every test. We need to be able to save intermediate step results as we run tests.

We are often sharing artifacts to our customers and prospects via public link ahead of a meeting. I want to be able to have the user just put it into full screen, without needing to pull the source html frame reference... this function should match the internal hatz artifact top bar widget. can we get our tenant branding on the public share too?

Claude Cowork is a game-changing product layer that uses the Claude LLM to act as a collaborative agent that can work alongside you — performing tasks, interacting with tools, and operating more autonomously than a simple chat interface. This would be a valuable extension of the power of Hatz.

Right now, anything we publish goes into the broader community marketplace, which isn't the right fit for some client-specific tools. We'd like the ability to publish apps and agents to a private or partner-scoped marketplace, something visible only to the tenants we manage, not to all Hatz customers. This could look like a "My Partner's Apps" section in Workshop. Some folks are hesitant to publish workflows broadly when it means exposing them to every Hatz customer. A partner-scoped marketplace would give us a path to share those tools with the right people without putting them in the open.

We would love to have the option of adding websites as sources when building an agent.

===================== Current Behavior: ===================== Currently, when an AI App, Agent, or Workflow includes an integration (such as AutoTask, ScalePad, or other Hatz integrations), each individual user who wants to use that workshop item must also have that same integration connected to their own personal Hatz account. The integration is tied to the user, not to the workshop item itself. This means: If you create a "Customer Support Agent" using AutoTask, every user of that agent needs their own AutoTask connection. Users cannot leverage a pre-configured integration — they must set it up themselves. There's no way to create a "company-owned" agent with its own integrations that users can consume without needing their own accounts tied to those services. ===================== Desired Behavior: ===================== We want the ability to assign integration skills directly to an App/Agent/Workflow (workshop item) so that: Integration Ownership at the Item Level — Integrations are attached to the workshop item itself, not the individual user consuming it. No User-Level Integration Required — End users can use the workshop item without needing to connect the integration to their own account. The item brings its own integration credentials. Isolated User Access — Users can interact with the workshop item for its intended purpose, but: - They cannot modify the integration settings. - They cannot access the integration directly. - They cannot use the integration for unauthorized purposes. - The integration belongs to the item/creator, not the user. Read-Only or Controlled Permissions per Skill — Admins can define what level of access the workshop item has to the integration via the instructions/prompt (read-only, write, full), and this is enforced regardless of what the user attempts. ===================== Use Case: ===================== Example: MSP Customer Support Agent An MSP creates a "Customer Support Assistant" App that uses AutoTask to: - Look up a customer's existing tickets and summarize them in less technical terms With Pre-Configured Integrations: - The MSP connects AutoTask to the App itself (not to each user's account). - End customers (or internal staff) log in and use the App without needing their own AutoTask connection. - The App uses the MSP's AutoTask credentials to perform actions. - Users can get ticket status and create tickets, but they cannot: - Access the AutoTask integration directly - Bulk-export all tickets - Delete records - Modify the integration settings This allows the MSP to centrally manage integration access while still enabling users to accomplish legitimate tasks through the workshop item — without exposing the integration itself.

As an MSP, we need the ability to create workflows, apps, or agents once and deploy them to multiple client tenants without manual replication. Currently, we must create individual copies for each tenant, and when updates are needed, we have to manually replace each copy making it difficult to track which clients are running which versions and keep them updated. Proposed solution: Implement a template or "master" system where MSPs can maintain a single master version of a workflow, app, or agent and push updates to all or selected client tenants simultaneously. This would streamline our deployment of apps, agents and workflows, ensure consistency across the tenants, and eliminate the burden of tracking version history across multiple tenants.

Add ability to test specific steps inside a workflow without needing to run in entirety.

I noticed that you can choose different LLM's but it would be super beneficial to be able to invoke Agents for steps in workflows.

We need to be able to add more than 3 tools to an agent- 3 is not enough for a modern organization. This is required for feature parity with other systems.