Website copilot workflow connectors
Use a Connector node with Digital Adoption Copilot to send a workflow step to authorized website-copilot panels. The workflow runner must be signed into Flolah and entitled to run the workflow. The website owner must enable workflow capability.
First working workflow test: Inspect one copilot
- In Flolah, create or open a workflow. Add a Connector node, select Digital Adoption Copilot, then choose Inspect.
- In the intended website's copilot, open Connections. The website owner must have enabled workflow access for this registration.
- Click Link this copilot to my Flolah workflows and copy the generated code. Its redemption window is two minutes by default; generate it when the workflow editor is ready.
- Return to the node. Paste the code into Copilot workflow link code, then click Link copilot as new group. To add another separately authorized panel later, select the existing group and use Add copilot to selected group.
- Select that Workflow target group and the website under Websites. Keep the default All authorized active instances on selected websites for this one-panel test.
- Enter: Inspect the current page's supported fields and navigation. Do not fill or save.
- Save draft → Publish → Run while the intended website panel stays online. Check the panel's chat and the workflow run audit for its response.
- For the next run, reuse the saved group and website selection. You do not need a new code for each run. Reconnect or explicitly authorize a panel again only when its authority has expired, been revoked or cannot be restored.
The code belongs in the link-code field, not the group-ID field. A successful Inspect demonstrates delivery and a structural response; it does not prove a saved business task. Start here before moving to Prepare, Fill or an owner-bound Submit with the required Action Policy.
Persistent group, separately authorized panels
The saved Workflow target group and Websites are the durable workflow configuration. You do not create a group for every run. Each run resolves the group's currently authorized online panels.
Link this copilot in a website panel creates a short-lived authorization code. In the node's Website copilot targets, enter that code and choose Link copilot as new group, or select an existing group and Add copilot to selected group. This authorizes the particular panel for the signed-in user's group. Knowing a group ID, owning the website or visiting the same domain does not authorize another visitor.
This is separate from peer pairing. Two copilots may pair for visitor-confirmed handoffs. A server workflow can target one directly authorized panel without pairing it with another. Visitors may use peer pairing without a Flolah account; running a Flolah workflow still requires the runner's signed-in entitlement.
Why does the link code expire?
The displayed expiry is for a one-use authorization code, two minutes by default. Redeeming it links the intended panel; the later expiry of that code does not remove the saved workflow group.
The group has its own lifetime. The current panel defaults to four hours and offers Until revoked on this browser. The shared UI labels this Pairing lifetime, although direct workflow linking uses it too. A group's own expiry or revocation stops delivery; this is different from the short code expiry. Do not regenerate a group merely because its already-redeemed code expired.
Configure the node
- Select Digital Adoption Copilot and an action: Inspect, Summarize, Prepare, Navigate, Fill, Submit, Status or Cancel.
- Choose a saved group and one or more websites. Refresh online copilots if needed.
- Choose all authorized active instances on those websites, or exact active instances. This never means every visitor on the domain.
- Enter the instruction and any authorized task/result handles. For Submit, select the exact owner-reviewed native action binding ID.
- Set bounded delivery validity, execution timeout and fan-out, then Save draft and Publish before running.
Prepare proposes fields for visitor review. Fill and Submit require the effective Flolah Action Policy. An autonomous grant can permit a workflow's fill path without a visitor clicking the ordinary field-review button; approval-required and prohibited operations remain gated. A submission binding is necessary for an unknown native Save control to become eligible, but is not sufficient to authorize a workflow action. Hosts may autosave on field entry.
Delivery and results
All captured recipients must succeed. Closed, disconnected, busy or unauthorized targets fail the step. Expiry does not queue the instruction for a future visitor. A saved group can outlive a connection, but cannot extend expired/revoked consent. Reconnect or explicitly authorize the intended panel again when necessary.
The recipient chat shows the workflow instruction and result. The run audit identifies targets and per-recipient outcomes. Inspect reports supported fields and navigation without entered field values. An acknowledgment or completed fill is not proof of saving: reopen the host record and verify it. Check an uncertain write's outcome before retrying.
Keep private document passages and extracted values in task context and pass authorized handles. Do not place full private files or their contents in a persistent workflow definition. End task clears active context and access immediately. Original uploads are queued for deletion; extracted passages await the separate 24-hour private index-retention cleanup. Ending a task does not undo host records or automatically revoke the saved group.
See Workflows, Digital Adoption, and Policies.
Outcome requirements and recovery
The Copilot node's Required outcome selects the existing effect contract,
verified field/navigation state, website-reported Save, or a trusted saved-record
receipt. Choose the requirement that matches the action and host integration.
A missing stronger proof fails the step even if the website displayed a success
message. Browser-supplied success booleans cannot create a business-verified result.
The optional host callback is getActionOutcome; its backend-signed receipt uses
purpose adoption_action_outcome and binds the current action, proposal, session
and path. It is separate from the verified-learning receipt.
The recipient conversation waits for the coordinator's outcome acknowledgement before announcing completion. Content-free run results include stage, target, evidence level and applied field count; private values remain behind task handles. Progress frames are bounded. Saved workflow groups still target current authorized online panels; peer pairing remains optional for server delivery.
Do not rerun an uncertain write automatically. Content-free action guards and workflow-operation tombstones reject replay after process recovery. A refreshed connection does not restore ended files, reuse approval or replay failed commands. For dependent forms, each new stage uses current controls and policy; the bounded continuation stops for unsupported or ambiguous states. A native Save can leave fields populated: navigation treats only matching, successfully submitted local values as acknowledged; a later edit remains a draft.
Using the copilot workspace
In the website copilot, open Connections to create a workflow link code. Peer pairing is optional. In Flolah, add a Copilot connector node and link the code to a new or existing persistent target group, then select the intended website(s). The code authorizes initial linking and expires; the saved target group is reused across runs. Only the workflow user's authorized online browser clients receive commands. Keep those website tabs open. Offline steps fail immediately and are not delivered to a later visitor.
The website Workflows tab shows the current run/step/outcome. Its instruction and response also appear in Chat. Action Policies still decide whether an effect requires a visitor review or is authorized for autonomous execution. For peer-to-peer handoffs, set up consent in Connections, then use @recipient in the single Chat composer; do not use workflow linking as peer-sharing consent. Private files and End task are in Tasks, separate from the saved workflow target group's lifetime.
Private copilot-to-copilot tasks and goals
No file is required. Pair the two open panels under the same website owner and confirm in both. In Connections, Inspect this copilot requests the other panel's current supported forms, required fields and navigation; it returns structure without current values or browser writes. The response appears in both chats and becomes private task evidence for subsequent planning. It is not published into either website's shared knowledge.
To continue work in another tab, select private-context sharing consent, optionally select Include current nonsecret form values, then use @ in the normal Chat composer to choose the current paired recipient and describe the task. The recipient interprets the incoming instruction with its own live page and shared task evidence. Read-only inspection plans can complete without a write review. Plans containing changes are shown for review; field changes, navigation and Save keep their existing confirmations. An active recipient goal is not replaced: finish/cancel it before selecting Review received goal. A request can be declined.
A goal can also include a peer step selecting one currently observed recipient. Review Send to paired copilot, choose whether to include current nonsecret form values, and send. The source shows Waiting for the paired copilot while the recipient reviews and executes its own goal. Source progress advances only after a validated inspection response or a completed recipient goal with recorded outcomes. Example: fill and save Customer in tab A, inspect Note in tab B, then use the shared Customer name/email to fill and save Note there. A receipt is browser/host-reported evidence; it is not independently verified business completion unless that integration exists.
Pairing is required for this visitor-to-visitor exchange; server workflow delivery continues to use separately linked workflow groups. Different website indexes remain isolated. Each RPC checks exact live source/recipient, bilateral pairing, owner, website/session and private task access. Values come only from supported visible nonsecret controls when explicitly selected. Pair revocation, changed permissions, task end, cancellation or disconnect invalidates pending work and associated pending goal approvals. Unfinished work fails without automatic replay or delivery to a replacement visitor. Private peer context is bounded and expires with its task; no attachment or shared document upload is implied.
Conversation recovery and planning scope
Choose Plan a task / Goal plan before sending a coordinated multi-website request. Current page & task prepares one current-page proposal; its review identifies this boundary and offers Plan complete task to preserve the full request in Goal plan. Plan a task can reuse the last request for review and never starts or approves it automatically. Remove already completed effects before starting a new plan.
A dropped live connection invalidates private pending work but retains historical messages. Reconnection never replays a fill or Save. Explicit End task, conversation reset and actual authorization expiry have separate privacy behavior. A checker failure pauses the operation; it does not itself clear the conversation.