Copilot

Copilot is Innflow's workflow-building assistant. Use it from Home to turn a request into a new workflow or table, or inside the editor to understand and change the workflow already on the canvas.

Home

The Home composer is the fastest way to start. Describe the system you want, select relevant apps, and attach workspace resources, files, or pasted text. Copilot can draft a workflow or table and hand it into the appropriate editor for review.

Copilot uses its configured model automatically. You can dictate a prompt with the microphone and continue the same conversation as generated artifacts appear. Model selectors inside workflow AI nodes configure those nodes, not Copilot itself.

Editor Copilot

Open Copilot from the workflow editor to work against the live canvas. It receives a redacted snapshot of the workflow's nodes, connections, and configuration so its suggestions stay grounded in the current state.

What the Copilot Can Do

Build workflows

Describe what you want to automate and the Copilot will create the full workflow with appropriate triggers, actions, and connections.

Add nodes

Ask the Copilot to add specific nodes to your existing workflow.

Configure nodes

Tell the Copilot how to set up a node and it will fill in the configuration fields.

Get suggestions

The Copilot analyzes your current workflow and suggests next steps based on what you have built so far.

Explain workflows

Ask for a plain-language explanation of an unfamiliar workflow or node path.

Test and repair

Run an approved test, monitor the exact execution, and apply bounded safe configuration repairs when enabled.

Context Aware Suggestions

When you open the Copilot, it reads your current workflow state (what nodes you have, how they are connected, what is configured) and tailors its suggestions. For example:

Empty workflow: "Add a trigger to get started" or "Build a workflow from a description"
Has trigger, no actions: "Add an AI node to process the input" or "Connect to Slack to send notifications"
Complete workflow: "Run the workflow" or "Add error handling"

Context and continuity

Copilot supports:

Separate conversation threads
File and pasted-text attachments
App and workspace-resource references
Voice dictation
Persistent conversation history
Relevant saved preferences and corrections
Visible activity and tool traces for actions it takes
Positive or negative response feedback

Live workflow state takes precedence over saved conversation memory.

Recovering a failed workflow save

If Copilot finishes its work but the final workflow save fails, Workflow not saved appears with a Retry save button. The completed response and canvas edits remain available in the open editor.

Choose Retry save to retry persistence without rerunning your message or its tools.
You can also use the workflow toolbar to save. A successful manual save clears the Copilot save warning.
If you switch workflow tabs, return to the affected workflow to recover its save. Each workflow keeps its own recovery state.
A revision conflict still needs reconciliation; retrying does not overwrite another editor's changes.

Keep the editor open until saving succeeds. The browser warns when leaving with a pending Copilot save failure, but that warning is not a backup: ignoring it and reloading can discard unsaved edits. This recovery applies to workflow saving; generation failures and conversation-history save failures have their own error controls.

Test & Repair

When Test & Repair is enabled for the deployment, Copilot can start a real workflow execution after you approve the warning. A session can make up to three real attempts and can automatically change only explicitly safe configuration fields.

Test & Repair runs are real executions. They can send messages, update external systems, and consume credits. Structural changes, credentials, destinations, operations, schedules, deployment state, and other sensitive changes require separate confirmation.

Copilot availability and advanced capabilities depend on your plan and workspace configuration.