Node: Workflow History
The Workflow History node automatically generates a PDF with the complete event history of the running instance. Unlike the Create PDF node, which lets you compose a custom document, this node produces a structured report generated by the system itself — no content configuration needed. You only set the page format and orientation.
The resulting PDF is an artifact available to subsequent nodes: it can be attached to emails, uploaded to file repositories, or included in approval emails.
What the History PDF contains
The generated document chronologically records all events of the workflow instance from start to the moment of generation, including:
- Instance start — when the trigger was activated and by whom
- Node entries and exits — each node executed throughout the flow
- Emails sent — recipients, subject, and timestamp of each send
- Approvals — who received, who responded, which outcome was chosen, and the approver's comment
- Requested form responses — forms sent and when they were responded to
- Conditional decisions — which path the If/Else node followed and why
- Status updates — texts defined by the Set Status node
- Timeouts reached — when a deadline expired without a response
- Errors — failures that occurred during execution
- Closure — instance completion, cancellation, or failure
The report uses the language configured in the space owner's account.
When to Use
Use the Workflow History node when the process needs to produce a complete and traceable record of everything that happened during execution. Common cases:
- Auditing and compliance — generate documentary evidence that all process steps were followed, with timestamps and identified responsible parties.
- Approval records — produce a report with the complete history of who approved, when, and with what comment, for internal control purposes.
- Process closure — attach to the completion email a document summarizing the entire instance trajectory for the parties involved.
- Support and troubleshooting — generate the history of a failed instance for technical diagnosis or analysis.
To capture the maximum number of events, position the Workflow History node near the end of the flow — after approvals, form submissions, and other actions. The closer to the end, the more complete the report.
Configuration
The Workflow History node has minimal configuration — the PDF content is generated automatically by the system. Only the page format is configurable:
| Field | Required | Description |
|---|---|---|
| Node label | No | Display name of the node on the canvas. Does not affect PDF generation. |
| Page format | No | Paper size for the PDF. Options: A4 (default) or Letter. |
| Page orientation | No | Paper orientation. Options: Portrait (default, vertical) or Landscape (horizontal). |
There is no file name or document body field: the system automatically defines the file name and the entire report structure based on the events recorded in the instance.
Node Output
The Workflow History node has a single output. After the PDF is generated and uploaded, the workflow automatically advances to the next connected node.
The generated file is available as an artifact in all subsequent workflow nodes. Common uses:
- Send Email: select the artifact in the attachment selector in the email body to send the complete history to stakeholders.
- Approval: attach the history to the approval email so approvers have full context before deciding.
- Upload to Google Drive / OneDrive: archive the report in a centralized repository for future access and compliance.
Difference from the Create PDF Node
| Aspect | Create PDF | Workflow History |
|---|---|---|
| Content | Defined by the user in the visual editor | Generated automatically by the system |
| File name | Configurable (supports variables) | Automatic (defined by the system in the account language) |
| Form variables | Yes — you insert {{field}} in the editor | No — content is structured automatically |
| Ideal use | Formal documents with custom layout (receipts, reports, contracts) | Audit reports and complete process traceability |
Best Practices
- Use at the end of the flow: positioning the node near closure ensures all significant events have been recorded before PDF generation.
- Combine with Send Email: send the history as an attachment in the completion email so stakeholders receive a formal process receipt.
- Archive with Google Drive or OneDrive: keep history reports in a centralized repository for easy retrieval and future audits.
- Does not replace Create PDF for formal documents: the history is a technical traceability report, not a formatted document for client presentation — for that, use the Create PDF node with a custom layout.