Co-Pilot Best Practices

Co-Pilot is available through the Workflow Canvas and is designed to help you build workflows faster. It can suggest actions, fix issues, and guide you step by step. These best practices will help you get the most out of it.

Be Specific with Your Prompts

• When asking Co-Pilot to add or change something, be clear about the node or action you want to work with

• If you do not already have the node selected, name it specifically in your prompt

• For example, say “Extract the email address from the Gmail trigger and add it to the Google Sheets action” rather than just “Extract the email”

Think Step by Step

• Imagine you are drawing the workflow on a whiteboard

• Think about the flow systematically:

  • How the data is ingested into the workflow

  • How the data moves through nodes inside the workflow

  • How the data is outputted at the end

• The clearer you are about each step, the better Co-Pilot can build what you need

Avoid Ambiguity

• Do not leave instructions open to interpretation

• Instead of saying “Connect this to that”, specify exactly what fields and outputs should be connected

• Precise language avoids errors and saves time later

Use Co-Pilot as a Guide

• Co-Pilot is not just for creating nodes

• You can ask it to explain what a workflow is doing

• You can ask it to suggest improvements

• You can use it to debug issues step by step

Review Suggested Changes

• Co-Pilot will show you the changes it has made

• Take time to review these suggestions and explore what was updated

• If you do not like the changes, you can decline or reverse them

Watch for Validation and Fixes

• Co-Pilot can highlight areas where validation is needed inside your workflow

• Keep an eye out for these prompts, as they help prevent broken runs

• You can also use Co-Pilot to fix errors directly, saving time on manual troubleshooting

💡 Think of Co-Pilot as a partner. It builds, explains, fixes, and suggests, but you are still in control of how your workflow works.