Portable execution evidence via .epi artifacts

[mohdibrahimaiml]

Feature Description

Flowise enables visual AI workflows, but execution traces remain internal (logs/state).

For audit and compliance use cases, workflows need portable, verifiable execution records.

I built a simple tool that wraps Flowise execution and generates a .epi artifact.

Repo: https://github.com/mohdibrahimaiml/flowise-epi-tool

This allows users to:

• capture workflow execution
• export it as a portable artifact
• share for auditing or verification

Would the team be open to supporting this as a custom tool or integration?

Feature Category

Integration

Problem Statement

Flowise workflows execute multi-step AI pipelines, but execution traces are limited to logs and internal state.

For audit, compliance, and debugging purposes, teams need portable and verifiable records of what actually happened during execution.

Current limitations:

• logs are not portable across systems
• logs are not tamper-evident
• difficult to share execution history with external stakeholders

This creates a gap for governance and audit-ready workflows.

Proposed Solution

Introduce a custom tool or plugin layer that allows exporting workflow execution as a portable artifact.

A reference implementation (EPI Recorder) generates .epi files that contain:

• input data
• intermediate steps
• validation results
• final outputs

Integration options:

• custom Flowise tool node
• post-execution hook
• export API

Users could simply add an "EPI Recorder" node at the end of a workflow to generate an artifact.

This would enable:

• audit-ready workflows
• reproducibility
• external verification

Mockups or References

Reference implementation:

• https://github.com/mohdibrahimaiml/flowise-epi-tool
• https://github.com/mohdibrahimaiml/epi-recorder

The Flowise tool simply wraps execution and outputs a .epi file.

Additional Context

This aligns with a broader gap across AI guardrails and workflow systems where "audit logging" is present but not implemented as portable, verifiable artifacts.

Positioning this as an optional integration keeps Flowise simple while enabling compliance-focused use cases.