How do I install the Workflows History skill?

Run npx skillmds@latest add zapier/workflows-history in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Workflows History safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Workflows History?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Workflows History free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Workflows History?

zapier (@zapier) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Workflows History by zapier — Agent Skill

Name: Workflows History
Author: zapier

Workflows History

Show run history for a specific durable workflow using the Zapier SDK experimental Code Workflows commands. Use when the user asks for run history, execution history, what happened with this Zap, or how a workflow fired.

zapier 16e5a1d 2.7 KB Updated Sep 17, 2026

File contents

Zapier Workflows History

Use the public SDK CLI experimental command surface. Do not use zapier-sdk-code-substrate.

Compatibility Gate

Before using this skill, run the workflows-doctor bundle compatibility check. If workflows-doctor is not installed or cannot be loaded, run workflows-install or install workflows-doctor from zapier/agent-skills before continuing. If workflows-doctor reports SDK/skill drift, follow its refresh instructions, stop this skill invocation, reload the agent workspace if needed, and ask the user to rerun the original request.

Identify The Workflow

If the user provides a workflow ID, use it directly.

If the user refers to the workflow by name or description, list workflows first and find the matching ID:

zapier-sdk --experimental list-workflows --json

If multiple workflows match, show the candidates and ask the user which one they mean.

Fetch Run History

zapier-sdk --experimental list-workflow-runs <workflow-id> --json

Parse the JSON output. Useful fields may include id, status, started_at, finished_at, input, and output.

When the workflow ID is known, include the Zapier editor link:

https://zapier.com/durables-editor/<workflow-id>

Drill Into A Run

If a single deployed workflow run failed or the user wants step-level detail:

zapier-sdk --experimental get-workflow-run <run-id> --json

Use get-durable-run <run-id> only for one-off synthetic runs created by zapier-sdk --experimental run-durable, not for deployed workflow runs returned by list-workflow-runs.

If a manual trigger response returns a trigger ID before a workflow run ID is available, bridge from trigger to run:

zapier-sdk --experimental get-trigger-run <trigger-id> --json

Summarize the failure, status, timing, input, output, and any step error details that appear in the response. Avoid dumping raw JSON unless the user asks for it.

Draft State

Runs execute published versions — unpublished draft edits never show up in run history. If the user expects a recent change to be reflected in runs and it isn't, check for an open draft holding that change:

zapier-sdk --experimental list-workflow-drafts <workflow-id> --json

If an open draft exists, tell the user their change is unpublished (note last_edited_at and the editor link) rather than concluding the workflow is broken.

---name: workflows-historydescription: Show run history for a specific durable workflow using the Zapier SDK experimental Code Workflows commands. Use when the user asks for run history, execution history, what happened with this Zap, or how a workflow fired.license: MIT---# Zapier Workflows HistoryUse the public SDK CLI experimental command surface. Do not use `zapier-sdk-code-substrate`.## Compatibility GateBefore using this skill, run the `workflows-doctor` bundle compatibility check. If `workflows-doctor` is not installed or cannot be loaded, run `workflows-install` or install `workflows-doctor` from `zapier/agent-skills` before continuing. If `workflows-doctor` reports SDK/skill drift, follow its refresh instructions, stop this skill invocation, reload the agent workspace if needed, and ask the user to rerun the original request.## Identify The WorkflowIf the user provides a workflow ID, use it directly.If the user refers to the workflow by name or description, list workflows first and find the matching ID:```bashzapier-sdk --experimental list-workflows --json```If multiple workflows match, show the candidates and ask the user which one they mean.## Fetch Run History```bashzapier-sdk --experimental list-workflow-runs <workflow-id> --json```Parse the JSON output. Useful fields may include `id`, `status`, `started_at`, `finished_at`, `input`, and `output`.When the workflow ID is known, include the Zapier editor link:```texthttps://zapier.com/durables-editor/<workflow-id>```## Drill Into A RunIf a single deployed workflow run failed or the user wants step-level detail:```bashzapier-sdk --experimental get-workflow-run <run-id> --json```Use `get-durable-run <run-id>` only for one-off synthetic runs created by `zapier-sdk --experimental run-durable`, not for deployed workflow runs returned by `list-workflow-runs`.If a manual trigger response returns a trigger ID before a workflow run ID is available, bridge from trigger to run:```bashzapier-sdk --experimental get-trigger-run <trigger-id> --json```Summarize the failure, status, timing, input, output, and any step error details that appear in the response. Avoid dumping raw JSON unless the user asks for it.## Draft StateRuns execute published versions — unpublished draft edits never show up in run history. If the user expects a recent change to be reflected in runs and it isn't, check for an open draft holding that change:```bashzapier-sdk --experimental list-workflow-drafts <workflow-id> --json```If an open draft exists, tell the user their change is unpublished (note `last_edited_at` and the editor link) rather than concluding the workflow is broken.

Frequently asked questions