Review Zapier workflow history with AI
Inspect previous runs of one authorised workflow, identify the relevant event and distinguish the published version from an unshipped draft.
To review Zapier workflow history with AI, make sure the name points to the right workflow. A test process and the live order process may differ by only a word. The workflows-history guide uses the supplied identifier or lists plausible matches before examining runs and their recorded events.
A change saved in a draft yesterday cannot explain a failure in the published version unless it was actually shipped. Compare the run time and revision before diagnosing the wrong change. Retrieve only the input or output details needed, since a connected service may have written sensitive information to the history.
What it does
- Find the correct workflow by name or identifier
- List previous runs and their status
- Inspect start and finish times
- Review relevant events from a failed run
- Separate published behaviour from an open draft
Install and use
- Install the official Zapier Workflows skills, compatibility doctor and SDK CLI. Use an authorised account with Workflows Early Access and permission to inspect the workflow’s runs.
- Ask “Review the latest failed order-processing run. Show the time and relevant event, but omit customer data from the summary.”
- Check the workflow ID and published version and share only the necessary evidence with authorised colleagues.
FAQ
Source
Made by Zapier. Original skill: workflows-history, published on GitHub under the MIT licence.
View on GitHub