Composer & Generative AI
How Composer assists workflow editing, what to verify before you apply changes, and how external AI providers are involved.
Creators building and publishing workflows.
Composer is the AI-assisted editing panel inside Workflow Studio. You describe what you want in plain language, review proposed graph changes, and apply them only when they look right.
Composer uses generative AI. Suggestions can be wrong, incomplete, or unsuitable for your product. You are responsible for what you apply and what you publish.
Effective date: May 26, 2026 Last updated: May 26, 2026
What Composer is#
Composer helps you inspect the current workflow, propose supported edits (add blocks, update settings, connect nodes), validate those edits against Edgaze rules, and explain what it intends to change.
Composer is not a general chatbot, legal advisor, or guarantee that a workflow will run correctly in production. It does not silently rewrite your canvas without review.
External AI providers#
Composer sends your prompt and relevant workflow context to third-party model providers to generate responses. Edgaze does not operate those models. Providers, versions, and routing can change.
Your use is subject to Edgaze policies and the provider's terms. Do not submit secrets, passwords, or data you are not allowed to share.
How Edgaze keeps control#
The model proposes structured actions. It does not get unrestricted write access to your canvas.
Edgaze validates proposals against supported blocks and connection rules before anything applies. Destructive changes can require your explicit approval. Limits on turns, tool use, and graph size reduce runaway automation. Where supported, you can undo recent Composer-applied changes from the changes panel.
If you edit the canvas while Composer is working, Edgaze tries to detect conflicts so manual work is not overwritten quietly.
Composer cannot edit locked or read-only workflows.
What we do not guarantee#
Composer may misunderstand your intent, produce suboptimal graphs, miss policy or compliance needs, or be unavailable. Confident wording is not proof of correctness.
Your responsibilities#
Review diffs and behavior before you apply or publish. Test with representative inputs. Do not paste API keys or unnecessary sensitive data into prompts. Decide whether each suggestion should be applied, edited, or rejected.
Data handling#
Prompts, attachments where supported, and workflow context may be processed by Edgaze and external providers to operate the feature. See the Privacy Policy for broader data practices.
Related policies#
- Content Disclaimer
- Terms of Service
- Acceptable Use Policy
- Privacy Policy
- Workflow Run Policy
- Billing guides
- Workflow Studio
Contact#
Questions: [email protected]
Was this useful?
Your response helps us improve the documentation.
Related builder documentation
How Workflow Studio, Composer, Templates, and API Vault fit together in Edgaze.
Build, test, and publish your first Edgaze workflow without learning every block at once.
Build, publish, and integrate a workflow that turns a company website into a structured sales-research brief.