Workato Makes Genies, Skills, and Knowledge Bases Workspace-Wide

Workato has removed the project boundary for Genies, Skills, and Knowledge Bases. What was previously limited to a single project can now be assembled, shared, and reorganised across an entire workspace. For teams that have been working around that constraint, this is a meaningful structural change.

What Was the Problem Before

In Workato’s agentic tooling, a Genie is an AI agent that uses Skills (defined actions it can take) and Knowledge Bases (data it can query) to handle requests. Until this update, all of those components had to live in the same project as the Genie itself.

In practice, teams building multiple Genies across different projects — say, one for HR workflows and one for finance — had two options: duplicate the shared components in each project, or work with separate sets of Skills and KBs that could drift out of sync. Neither is good if you’re trying to maintain consistent, auditable automation at scale.

What’s Changed: Four Specific Capabilities

Cross-Project Skills and Knowledge Bases

Builders can now add Skills and attach Knowledge Bases from any project in the workspace to any Genie. A skill library maintained in one project can power Genies living elsewhere, without copying anything. This is the change most teams will feel immediately — it allows a single canonical set of skills rather than diverging copies.

Cross-Project Events and Tasks

Recipes can now send app events to Genies in other projects and assign tasks to them across project boundaries. This matters for teams building multi-step agentic workflows where different stages are logically organised into separate projects. Previously, cross-project handoffs between Genies weren’t possible through the standard event and task routing — you’d need workarounds. That constraint is gone.

Cross-Project Knowledge Writes

Knowledge recipes — the recipes that populate Knowledge Bases — can now write to KBs in other projects. This enables a single-source-of-truth architecture: one set of ingestion recipes populates a shared KB, and multiple Genies across different projects read from it. Without this, teams had to either duplicate ingestion logic or accept that Genies in different projects had access to different (potentially stale) knowledge.

Move Assets Freely

Skills, Knowledge Bases, and Genies can now be moved between projects without breaking existing links. This is operationally important and often overlooked in capability announcements. Reorganising a workspace was previously a risky operation — moving a Skill that was referenced by a Genie in another project could break things. Now the links survive the move.

Who This Affects

Teams in two situations will notice this most:

• Teams that duplicated assets to work around the single-project limit. The immediate task is consolidation: identify the duplicates, pick the canonical version, move it to a shared location or leave it where it is and delete the copies. The move-without-breaking-links change makes this feasible to do without a freeze window.
• Teams planning new Genie deployments. Workspace-wide reuse changes the design question. Instead of “what does this Genie need in its project?”, the question becomes “what shared assets already exist in the workspace that this Genie can use?”

Teams that have only built a single Genie in a single project will see less immediate impact, but the architectural change still matters if they’re planning to expand.

Connection to Broader Workato Agentic Direction

This update is part of a broader pattern in how Workato is developing its agentic layer — moving from isolated, project-scoped components toward workspace-wide composability. The Workato Genies Microsoft Teams channel support update earlier this year was a similar step: expanding where Genies can operate, rather than adding new capabilities within existing boundaries.

The underlying direction is that Genies are becoming more like shared infrastructure and less like one-off automation components. Designing for reuse from the start — consistent Skill naming, well-maintained KBs, clean project organisation — will matter more as that direction continues.

Where to Start

Workato’s updated Agent Studio documentation covers the workspace-wide asset model. If you’re planning a consolidation of existing Genies or Skills, reviewing it before making changes is worthwhile — the documentation covers how cross-project links behave and what to expect when moving assets.

Source: Genies, Skills, and Knowledge Bases Now Available Across the Workspace — Workato Product Hub Changelog. This article is a workflow interpretation of that release note.