Build with Copilot
Use conversation to help create, explain, and refine a workflow.
IN THIS LESSON
- Give Copilot a concrete goal and useful constraints.
- Review the resulting workflow before running it.
Describe the outcome
Specify what starts the workflow, what information it receives, and what should happen at the end. Include the apps or workspace resources it should use.
Build a workflow for a new support request. Check whether the request includes an email address. Save complete requests to a table, and route incomplete requests to a separate path for review.
Work in small changes
Ask Copilot to explain the current workflow, add a step, or help repair a specific failure. Review the changed node fields and connections. Connected accounts, permissions, and required configuration still matter.
Review before execution
Confirm the chosen destination, the data sent to each service, and what happens when a step fails. A helpful generated graph still needs a controlled test.
Separate completion from saving
A completed Copilot response does not by itself prove that the workflow was saved. If Workflow not saved appears, keep the editor open and choose Retry save, or save from the workflow toolbar. This retries the save without asking Copilot to repeat completed actions.
If saving still conflicts, preserve your edits and review the latest workflow. Reloading can discard unsaved work. See save recovery before retrying the original prompt.
Try it
Ask Copilot to explain a workflow you already understand. Then request one small change and compare the graph and configuration before running it.