How to import a Digital Worker from the Marketplace
Overview
Agentic Studio allows users to import pre-configured Digital Workers into their workspace. Importing starts from an existing packaged configuration that includes core components such as instructions, tools, skills, triggers, and integration references, providing a proven starting point that can be adapted to a specific environment.
Imported Digital Workers are not automatically ready to run. Environment-specific details, particularly connector and integration references, must be configured before the import can be completed.
Import Sources
When importing a Digital Worker, users can choose from three sources.
Marketplace: The marketplace contains reusable Digital Workers published by approved contributors. Marketplace workers represent complete configurations, not partial starters. Selecting a worker from the marketplace brings in the full configuration, with the requirement that all integration references are reconnected before the import is finalized.
My Templates: My Templates contains Digital Workers that have been exported and saved as templates within the tenant. Any user in any workspace belonging to the same tenant can export a Digital Worker and save it as a template, making it visible across all workspaces in that tenant. This supports standardization and reuse of common worker patterns across teams.
Upload: Users can upload a packaged Digital Worker from a local file. This supports scenarios where a worker has been prepared offline or transferred from another environment.
The Import Flow
Importing a Digital Worker follows a consistent sequence regardless of the source.
Once all required configuration is complete, the import finalizes and the Digital Worker is available in the workspace's test environment for further configuration and testing.
After Importing
Once imported, the Digital Worker lands in the test environment. From there it can be configured further, tested, and refined before any version is promoted to production. The imported configuration provides the starting structure; the test environment is where it is adapted to the specific operational context it will run in.
Last updated
Was this helpful?