Bundle
Zip sources + report + JSON
Packages everything from a job (the original uploaded files, the finished report, and the structured data) into a single downloadable zip.
How it works
By the end of a job you often have several pieces: the files someone submitted, the report you produced, and the structured data behind it. Handing those over one by one is clumsy. Bundle gathers them into one archive.
It rolls the source files, the finished report, and the JSON data (the machine-readable version of the extracted values) into a single zip. That gives you one clean deliverable to send to a client, hand to a colleague, or keep as a complete record of what the job did.
It usually sits near the end of a flow, right before the file is delivered or stored, so the zip captures the finished results rather than a work-in-progress state.
Common use cases
Real situations where this node earns its place in a flow.
Package everything to hand off
Zip the source documents, the report, and the data JSON into one archive to deliver.
Assemble a case file
Bundle all artifacts of a job together for records or compliance.
Send one download
Give a customer a single zip instead of many separate files.
Bundle in a workflow
A simple example of where this node sits in a flow.
What you set up
- Place it after the steps that produce your report and data so there is something to gather.
- Let it collect the job's source files, report, and structured JSON into one zip.
- Route the zip to a delivery or storage step for download or handoff.
Common questions
What ends up inside the zip?
The original files that were submitted, the finished report, and the structured JSON data, so the archive is a complete record of the job in one download.
When in the flow should it run?
Near the end, after your report and data exist. Placed too early it would bundle results that have not been created yet.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
includeSourceFilesInclude the original uploaded source files in the zip.
Type: booleanDefault:trueincludeExtractedJsonInclude extracted JSON output in the zip.
Type: booleanDefault:truefilenameTemplateTemplate for the output zip filename.
Type: stringDefault:{merchant}-{date}.zip
How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.
{
"id": "bundle",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "bundle",
"kind": "processor",
"title": "Bundle",
"subtitle": "Zip sources + report + JSON",
"config": {
"includeSourceFiles": "true",
"includeExtractedJson": "true",
"filenameTemplate": "{merchant}-{date}.zip"
}
}
}