BURKI WORKFLOW EXPORT REVIEW WORKSHEET
Free planning resource. Checked October 11, 2026.

Purpose: inspect a downloaded server-saved workflow bundle and record
what it preserves. Not an import tool, complete account backup, tested
recovery procedure or proof of a voice call. No provider action, call,
production save or restoration was performed for the fictional example.
Later voice usage and other operations have separate costs/prerequisites.

1. IDENTIFY THE REQUEST
Reason for exporting:
Authorized account / organization (private receipt):
Workflow name / identifier:
Responsible operator:
Approved storage location:
Authorized recipient, if a sharing copy is needed:
Export request / local download date and time:
Actual filename:
Actual exported_at from the JSON (server UTC):

Current entry: Assistants -> existing Guided assistant -> Open -> More -> Export.
Do not rely on a Flows sidebar. Export fetches server state; it does not
save or include local unsaved canvas edits.

2. RECORD THE PRE-EXPORT STATE
Displayed publication state:
Displayed Unsaved draft badge present? yes / no / unknown
Last known server-saved draft change:
Published version:
Local unsaved proposal, if any:
Whether an authorized save happened before export / evidence:
Other concurrent edits known / unresolved:

Do not save a production change merely to make an export include it.
If you need unsaved text preserved separately, use the approved process
and label it as a proposal, not a saved or published bundle.

3. INSPECT THE LOCAL JSON WITHOUT EDITING THE ONLY COPY
[ ] Downloaded file exists and opens as complete JSON.
[ ] format is burki.conversation_flow.
[ ] format_version recorded (current checked format is 1):
[ ] name matches the intended workflow:
[ ] graph inspected as SERVER-SAVED DRAFT:
[ ] published_graph inspected, or absence recorded:
[ ] published_version recorded, or absence recorded:
[ ] latest_version recorded:
[ ] versions list reviewed, including earlier graphs:
[ ] exported_at recorded; do not confuse it with a change or test time.

Version entries may include graph, version, label, published_at and actor_id.
A format version is not a published workflow version.
latest_version is not necessarily the selected published_version.
A publication timestamp is not an acceptance-test timestamp.

4. FICTIONAL HOURS-CHANGE EXAMPLE
Alder Desk published v2: closes 17:00.
Server-saved draft: closes 16:00.
Unsaved canvas proposal: closes 15:00.

Expected export:
- graph: saved 16:00 draft.
- published_graph: published 17:00 instructions.
- relevant v2 entry: 17:00 instructions.
- local unsaved 15:00 proposal: not added from the canvas.

This is fictional. No real hours, downloaded customer bundle or accepted
call is implied. Record your actual expected and observed values below.

Expected saved draft:
Observed graph value / evidence location:
Expected published graph / selected version:
Observed published_graph value / evidence location:
Expected omitted unsaved edit:
Observed omission or discrepancy:
Review outcome / responsible owner:

5. REVIEW ALL CONTENT BEFORE SHARING
Graph validation is not automatic redaction.
[ ] Current draft instructions and business details reviewed.
[ ] Published graph reviewed.
[ ] EVERY historical graph reviewed.
[ ] Internal contact details / private examples / identifiers reviewed.
[ ] Tool configuration and references reviewed.
[ ] Labels, actor metadata and other included content reviewed.
[ ] Recipient is authorized for the actual file contents.
[ ] Original receipt and any prepared sharing copy clearly distinguished.
Unresolved private/sensitive content:
Next owner / actual remedy, if needed:

Do not paste keys into workflow instructions. Do not assume a file is safe
because it has no top-level password field. Export does not revoke access,
rotate credentials or remove information from saved history.

6. DEPENDENCIES NOT ESTABLISHED BY THIS EXPORT
Base assistant voice mode / model / settings:
Provider credentials and policies:
Knowledge document contents and current approval:
Tool definitions / assigned actions / actual connections:
Account permissions / funding / limits:
Browser or telephone route / carrier prerequisites:
Call recordings, transcripts and acceptance evidence:
Dependency owner / current verification evidence:

A reference is not a portable copy or proof of a working connection.
The bundle is not a whole-assistant or organization backup.
No import/restore is performed by this worksheet. Any later import needs
its own authorized scope and verification. Do not assume an import creates
only an unpublished preview or restores external dependencies.

7. EXPECTED VERSUS OBSERVED FAILURE CHECKS
Case A: Unsaved canvas differs from saved draft.
Expected: Export reflects server-saved draft, not local unsaved proposal.
Observed / evidence / next owner:

Case B: Saved draft differs from publication.
Expected: Record graph and published_graph separately.
Observed / evidence / next owner:

Case C: Workflow has no publication.
Expected: Missing published state remains missing, not invented.
Observed / evidence / next owner:

Case D: Selected publication differs from highest version.
Expected: Distinguish published_version from latest_version.
Observed / evidence / next owner:

Case E: Private detail survives in an older graph.
Expected: Sharing review catches it; no automatic-redaction assumption.
Observed / evidence / next owner:

Case F: Referenced connection or Knowledge corpus is unavailable.
Expected: Dependency remains unverified; no restored-runtime claim.
Observed / evidence / next owner:

Case G: Download or JSON inspection fails.
Expected: Preserve actual error and do not label a partial prompt copy
as a successful complete export.
Observed / evidence / next owner:

8. ACTUAL RESULT
[ ] Downloaded bundle only
[ ] Local contents inspected
[ ] Draft/publication differences reconciled
[ ] Sharing review complete for the intended recipient
[ ] External dependencies reviewed separately (evidence):
[ ] Actual restored-runtime acceptance, if later authorized (evidence):
Outstanding differences / responsible owner:

Article: https://burki.dev/blog/export-burki-voice-workflow
Commercial context: https://burki.dev/use-cases/ai-receptionist
Costs for later relevant operations: https://burki.dev/pricing