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
bundle compatibility check. If
is not installed or cannot be loaded, run
or install
from
before continuing. If
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:
bash
zapier-sdk --experimental list-workflows --json
If multiple workflows match, show the candidates and ask the user which one they mean.
Fetch Run History
bash
zapier-sdk --experimental list-workflow-runs <workflow-id> --json
Parse the JSON output. Useful fields may include
,
,
,
,
, and
.
When the workflow ID is known, include the Zapier editor link:
text
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:
bash
zapier-sdk --experimental get-workflow-run <run-id> --json
Use
only for one-off synthetic runs created by
zapier-sdk --experimental run-durable
, not for deployed workflow runs returned by
.
If a manual trigger response returns a trigger ID before a workflow run ID is available, bridge from trigger to run:
bash
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:
bash
zapier-sdk --experimental list-workflow-drafts <workflow-id> --json
If an open draft exists, tell the user their change is unpublished (note
and the editor link) rather than concluding the workflow is broken.