Prompting to add existing repository file

Developers can use Co-Pilot for Automators to add existing files (ex. task bot, credential variable) from the Control Room by entering a natural language prompt.

Automation files, like forms and task bots, offer sophisticated function to automation flows, especially in process automation. Data files, like credential and global variables, store valuable data that can be referenced securely in automation. These files are organized by folders in the Control Room that can be referenced and added by developers with instructional prompts in Co-Pilot for Automators, when building automation.

The Co-Pilot page offers a conversation style dialog box where you can write your prompt as a set of instructions that describes the files you want to add. Through this interactive conversation, Co-Pilot for Automators accelerates development by reducing human effort of clicking in to settings and selecting files. This single interface also streamlines the creative process, by maintaining focus on automation results, rather than the required configurations.

Add existing file to a node in a process

Use the precise name and the file path in the instructions of your prompt, when adding a file to a node in a process (like Form or Bot tasks). If the path is not specified, Co-Pilot searches the current folder where the process exists. Co-Pilot responds to your instructions with a message describing results of the search for your files and any successful additions made to your automation. Surrounding these inputs with quotation marks help isolate file names from prompt instruction.

Example:
  • add a form step for "Bots\forms\purchase form"
  • add a bot step for "invoice bot"

Video demonstrates adding an existing task bot via prompt from the current folder, named Message bot.

Adding files with Co-Pilot for Automators is supported in the Bot editor. For example, you can build a bot to run another bot. When building, ensure the action first exists on the canvas. Then you can enter your prompt to update the action by attaching the file of the bot task to the action.

Best practices and response messages

After sending a prompt, developers might encounter results where more details are needed. Multiple matches might be found or the name you enter might not match results. Co-Pilot will specify the details needed for the file to be found with a response message. The following best practices help improve instructions entered in your prompt.
  • Consider using quotes around your inputs to specify the exact file you want to add. Quotes can help isolate file names from objects (ex. "Example" bot, "Example bot").
  • Reference your folder organization in the Control Room to identify the accurate path or name of the file to enter the correct reference in your instructions.
    Image demonstrates where to find the file path.

Review the following topic to see full details of response messages. See, Response messages from Co-Pilot for Automators