Back to Details

workflows-list

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Zapier Workflows List

Zapier工作流列表

Use the public SDK CLI experimental command surface. Do not use 
zapier-sdk-code-substrate
.
使用公开的SDK CLI实验性命令接口。请勿使用
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.
使用此技能前，请运行
workflows-doctor
包兼容性检查。如果未安装或无法加载
workflows-doctor
，请先运行
workflows-install
或从
zapier/agent-skills
安装
workflows-doctor
，然后再继续。如果
workflows-doctor
报告SDK/技能版本不一致，请遵循其刷新说明，停止此技能调用，必要时重新加载代理工作区，并请用户重新发起原始请求。

Check Prerequisites

检查前置条件

bash
zapier-sdk --version
zapier-sdk get-profile --json
zapier-sdk --experimental --help
If auth fails, ask the user to run 
zapier-sdk login
in an interactive terminal and retry.
bash
zapier-sdk --version
zapier-sdk get-profile --json
zapier-sdk --experimental --help
如果认证失败，请要求用户在交互式终端中运行
zapier-sdk login
并重试。

List Workflows

列出工作流

bash
zapier-sdk --experimental list-workflows --json
Parse the JSON output and format what the user asked for. Common useful fields may include 
id
, 
name
, 
enabled
, 
is_private
, 
created_by_user_id
, 
created_at
, 
updated_at
, 
description
, 
current_version
, and trigger-related metadata if present.
For each workflow with an 
id
, include the Zapier editor link:
text
https://zapier.com/durables-editor/<workflow-id>
Treat 
trigger_url
as account-sensitive: firing it invokes the workflow as the authenticated account, so while the token in the URL is no longer a standalone credential, it is still not something to print gratuitously. Do not print 
trigger_url
unless the user explicitly asks for it.
Check each entry in 
triggers[]
for 
details.webhook_url
, regardless of trigger type — its presence alone tells you there's a catch URL. Unlike 
trigger_url
, 
webhook_url
is meant to be shared — it's the URL the user pastes into the external service — so surface it plainly when present. Most triggers have no 
webhook_url
, and that is normal; do not flag its absence unless the user specifically expects one (for example they mention "Webhooks by Zapier"), in which case the installed SDK may predate this field.
bash
zapier-sdk --experimental list-workflows --json
解析JSON输出并按照用户的需求格式化内容。常用的有用字段可能包括
id
、
name
、
enabled
、
is_private
、
created_by_user_id
、
created_at
、
updated_at
、
description
、
current_version
以及触发器相关元数据（如果存在）。
对于每个带有
id
的工作流，需包含Zapier编辑器链接：
text
https://zapier.com/durables-editor/<workflow-id>
请将
trigger_url
视为账户敏感信息：触发该URL会以已认证账户身份调用工作流，因此尽管URL中的令牌不再是独立凭证，但仍不应随意打印。除非用户明确要求，否则请勿打印
trigger_url
。
无论触发器类型如何，请检查
triggers[]
中的每个条目是否包含
details.webhook_url
——该字段的存在仅表示存在捕获URL。与
trigger_url
不同，
webhook_url
是用于共享的——它是用户粘贴到外部服务中的URL，因此如果存在，请直接展示。大多数触发器没有
webhook_url
，这是正常情况；除非用户明确预期（例如提到“Webhooks by Zapier”），否则无需标记其缺失，这种情况下可能是因为安装的SDK版本早于该字段的引入。

Open Drafts

开放草稿

A workflow's published state is not the whole story — it may also have open server drafts, and an open draft always holds unpublished work (publishing consumes drafts). When the user asks about unpublished changes, in-progress work, or why the editor shows something different from what's live, check:
bash
zapier-sdk --experimental list-workflow-drafts <workflow-id> --json
Surface each open draft's 
slug
, 
last_edited_at
, and 
last_edited_by_user_id
, and whether its 
base_version_id
matches the newest published version (an older base means the draft predates the current live version). Include the draft's editor link: 
https://zapier.com/durables-editor/<workflow-id>/draft/<draft-slug>/workflow.ts
— the final segment is one of the draft's 
source_files
keys (
workflow.ts
in this bundle's flows). Do not fetch drafts for every workflow in a plain listing — it is one request per workflow; do it on request or for the workflows under discussion.
工作流的发布状态并非全部情况——它可能还存在未提交的服务器草稿，而开放草稿始终包含未发布的工作内容（发布操作会消耗草稿）。当用户询问未发布的更改、进行中的工作，或者为什么编辑器显示的内容与线上版本不同时，请检查：
bash
zapier-sdk --experimental list-workflow-drafts <workflow-id> --json
展示每个开放草稿的
slug
、
last_edited_at
、
last_edited_by_user_id
，以及其
base_version_id
是否与最新发布版本匹配（较旧的基础版本意味着草稿早于当前线上版本）。包含草稿的编辑器链接：
https://zapier.com/durables-editor/<workflow-id>/draft/<draft-slug>/workflow.ts
——最后一段是草稿
source_files
中的一个键（此包流程中为
workflow.ts
）。请勿在普通列表中为每个工作流获取草稿——每个工作流需要一次请求；仅在用户请求或针对正在讨论的工作流执行此操作。

Ownership Scoping

所有权范围

list-workflows
may return every workflow the authenticated user can see, including team workflows. If the user asks for "my workflows," first show the likely matches and explain any uncertainty rather than silently filtering by the wrong ID.
Known quirk: 
zapier-sdk get-profile
may return a UUID that does not match 
list-workflows[].created_by_user_id
, which may be a separate numeric user ID. If you cannot confidently map those IDs, say so and present the unfiltered list with enough context for the user to choose.
list-workflows
可能会返回已认证用户可见的所有工作流，包括团队工作流。如果用户要求查看“我的工作流”，请先展示可能匹配的结果并说明任何不确定性，而非错误地进行静默过滤。
已知问题：
zapier-sdk get-profile
可能返回一个UUID，与
list-workflows[].created_by_user_id
不匹配，后者可能是一个单独的数字用户ID。如果无法可靠地映射这些ID，请告知用户并提供未过滤的列表，同时附上足够的上下文供用户选择。

Last Run Time

最后运行时间

If the user asks for recent activity, fetch runs for each relevant workflow:
bash
zapier-sdk --experimental list-workflow-runs <workflow-id> --json
Use the most recent run. Be mindful of API volume for large accounts.
如果用户询问最近的活动，请为每个相关工作流获取运行记录：
bash
zapier-sdk --experimental list-workflow-runs <workflow-id> --json
使用最新的运行记录。请注意大型账户的API调用量。