Prompt Co-Pilot for Automators to automatically detect and map custom packages and custom connectors. Accelerate development, enforce standardized logic, and reducing maintenance across Automation 360 workflows.

Overview

Co-Pilot for Automators can recognize and use custom packages and custom connectors that are registered in your Control Room. When you describe a task in plain language, Co-Pilot will automatically detect relevant packages/connectors and insert the correct actions, map parameters, and create output variables exactly as it does for native Automation 360 packages.

Available in the Task Bot editor and API Task Editor, Cloud and On-Premises versions.

What This Means for You
  • Describe what you need in plain language and Co-Pilot will use your existing custom packages/connectors to build it.
  • Promote reusability and development best practices.
  • Work consistently across teams. Co-Pilot suggests the same approved packages everyone is using.

How It Works

The administrator enables custom packages for Co-Pilot from the Control Room admin panel. A JSON file can be uploaded that details the allowed list of packages/connectors you want Co-Pilot to use.
Image orients users to the interface in Admin settings where custom package and connector support can be enabled for Co-Pilot.

When enabled, Co-Pilot indexes each package actions and parameters. This means when you enter a prompt Co-Pilot matches your intent to the admin-enabled package, generates the action, and assigns it to your automation. If a package you reference is not available or you lack access, Co-Pilot responds clearly so you can follow up with your administrator.

After JSON file is uploaded, the same prompting best practices can be used to instruct Co-Pilot for custom packages/connectors. See, 프롬프트를 통해 자동화 구축하기.

This method also works for connectors configured and published from the Control Room. See, 사용자 정의 커넥터 만들기.

Getting Started
  • Administrator enables custom packages and connector support in the Co-Pilot configuration panel.
  • Developer opens a Task Bot or API Task and type a prompt referencing your custom package name with the functionality it provides.
  • Review the generated actions, confirm parameter bindings, and run your automation.