Use Co-Pilot for Automators to build a new automation by describing your automation scenario with a set of instructions.

Building a new automation can require tedious human effort when hunting and selecting all the elements needed, especially when many steps are required. Leverage Co-Pilot for Automators (Co-Pilot) to eliminate repetitive effort during development and quickly build the structure of a new automation with the necessary nodes or actions. You can then focus on custom configurations for your individual needs. Simply articulate your scenario with a natural language prompt.

Instructions for the structure

Your automation structure includes all the nodes or actions on the canvas to visualize the work flow of your automation and begin setting individual configurations. Co-Pilot cannot interpret abstract ideas and needs your instruction to specify the building blocks for your automation scenario.

Your instruction should describe your automation in terms of the elements used to reach your goal (nodes, actions, conditions, etc.). Co-Pilot is available for both process and bot automation.
  • For a process, instructions should specify the nodes and entities in your automation scenario. Prompting for a process
  • For a bot, instructions should detail all actions of the task, and any logic or conditions applied to actions that fulfill your scenario. Prompting for task bots

Best practices for building new automation

Your prompt should articulate the elements used in the scenario and the relationship they have to reach your end goal. Co-Pilot cannot interpret implied concepts, but it can recognize relationships between variables and files required for actions and nodes. Best results come from instructions that name the operations and elements that are used in the operations. The more specific your description, the better the output.

These capabilities are best used when including your full automation scenario in a single prompt. However, some long and complex automation requires dividing the scenario into multiple prompts. When dividing a scenario into multiple prompts, send sections of operations to include the relevant sequence and any conditions or relationships the operation should have. Then work on the finer configurations and mapping of specific nodes or actions.