Scenario Log Export Should Include Webhook Payloads and Module Execution Trace
Shawn Bradley
When I export scenario execution logs, the CSV only contains execution-level metadata — timestamp, status, operations count, and the detail link. There is no way to see:
- The webhook payload that triggered the execution (e.g. which event type came in)
- Which modules actually ran within each execution
- The input/output data for each module
This makes the exported logs essentially useless for debugging. The only way to see what happened is to manually click into each execution detail link one by one — which is not realistic when you have hundreds of runs per day across multiple webhook event types routed through a single scenario.
Requested enhancement: Include optional columns in the CSV export for webhook payload (or at least a summary field like event type), the list of module IDs that executed, and module-level error details if applicable.
This would make exported logs actually useful for troubleshooting, auditing, and monitoring production scenarios at scale.
Log In