pipefy-reports
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseReports
报告
Pipe reports and organization reports: discovery, CRUD, and async exports. 17 MCP tools.
管道报告(pipe reports)与组织报告(organization reports):发现、CRUD操作及异步导出。17个MCP工具。
Cross-cutting patterns
通用模式
- Build using
ReportCardsFilterandget_pipe_report_columns; useget_pipe_report_filterable_fieldsfor uncommon inputs.introspect_type - omits
get_pipe_reportsin the query (Pipefy can error when resolving it).cardCount - on writes like other mutation tools.
debug=true
- 使用和
get_pipe_report_columns构建get_pipe_report_filterable_fields;对于特殊输入,使用ReportCardsFilter。introspect_type - 在查询中省略了
get_pipe_reports字段(Pipefy解析此字段时可能会报错)。cardCount - 与其他变更工具一样,写入操作时设置。
debug=true
Pipe report tools
管道报告工具
| Tool (MCP) | CLI | Read-only | Purpose |
|---|---|---|---|
| | Yes | List all reports for a pipe. |
| | Yes | Single report data. |
| | Yes | Discover available columns for a report filter. |
| | Yes | Discover filterable fields for a report. |
| | No | Create a new pipe report. |
| | No | Update report name or filters. |
| | No | Two-step destructive. |
| | No | Trigger async export. |
| 工具(MCP) | CLI命令 | 只读 | 用途 |
|---|---|---|---|
| | 是 | 列出某个管道的所有报告。 |
| | 是 | 获取单个报告的数据。 |
| | 是 | 发现报告筛选器可用的列。 |
| | 是 | 发现报告的可筛选字段。 |
| | 否 | 创建新的管道报告。 |
| | 否 | 更新报告名称或筛选条件。 |
| | 否 | 需两步确认的破坏性操作。 |
| | 否 | 触发异步导出。 |
Organization report tools
组织报告工具
| Tool (MCP) | CLI | Read-only | Purpose |
|---|---|---|---|
| | Yes | List all org-level reports. |
| | Yes | Single org report data. |
| | No | Create an org-wide report. |
| | No | Update report config. |
| | No | Two-step destructive. |
| | No | Trigger async export. |
| 工具(MCP) | CLI命令 | 只读 | 用途 |
|---|---|---|---|
| | 是 | 列出所有组织级报告。 |
| | 是 | 获取单个组织报告的数据。 |
| | 否 | 创建全组织范围的报告。 |
| | 否 | 更新报告配置。 |
| | 否 | 需两步确认的破坏性操作。 |
| | 否 | 触发异步导出。 |
Export status & download
导出状态与下载
| Tool (MCP) | CLI | Purpose |
|---|---|---|
| poll via | Poll pipe report export status (after |
| poll via | Poll org report export status (after |
| | Export pipe audit logs (separate from card report exports). |
| 工具(MCP) | CLI命令 | 用途 |
|---|---|---|
| 通过 | 在执行 |
| 通过 | 在执行 |
| | 导出管道审计日志(与卡片报告导出相互独立)。 |
Steps — export a pipe report
步骤 — 导出管道报告
-
List available reports:MCP:
get_pipe_reports pipe_id=67890 -
Trigger the export:MCP:
export_pipe_report report_id=123 -
Poll until finished:MCP:
get_pipe_report_export export_id=<EXPORT_ID>Repeat every 5–10 seconds until the response indicates(orfinished).failed -
Download: use the signedfrom the finished export response over HTTPS (the MCP tool surfaces it in the payload).
fileUrl
-
列出可用报告:MCP命令:
get_pipe_reports pipe_id=67890 -
触发导出:MCP命令:
export_pipe_report report_id=123 -
轮询直至完成:MCP命令:
get_pipe_report_export export_id=<EXPORT_ID>每5-10秒重复执行一次,直到响应显示(或finished)状态。failed -
下载: 通过HTTPS使用完成导出响应中的签名进行下载(MCP工具会在返回结果中提供该链接)。
fileUrl
Steps — create a filtered pipe report
步骤 — 创建带筛选条件的管道报告
-
Discover filterable fields:MCP:
get_pipe_report_filterable_fields pipe_id=67890 -
Create the report with ashape (not a top-level
ReportCardsFilterarray):current_phaseMCP:create_pipe_report pipe_id=67890 name="Phase subset" filter='{"operator":"and","queries":[{"field":"current_phase","operator":"eq","type":"select","value":"<phase_id>"}]}'Use the exactstring from step 1. Invalid shapes are rejected before GraphQL with a message pointing atfield.get_pipe_report_filterable_fields
-
发现可筛选字段:MCP命令:
get_pipe_report_filterable_fields pipe_id=67890 -
使用结构创建报告(而非顶层的
ReportCardsFilter数组):current_phaseMCP命令:create_pipe_report pipe_id=67890 name="Phase subset" filter='{"operator":"and","queries":[{"field":"current_phase","operator":"eq","type":"select","value":"<phase_id>"}]}'使用步骤1中获取的精确字符串。若结构无效,会在GraphQL执行前被拒绝,并提示参考field。get_pipe_report_filterable_fields
Success criteria
成功标准
- (or
get_pipe_report_export) reaches a terminalget_organization_report_exportorfinishedstate.failed - Downloaded export contains the expected card/report data.
- (或
get_pipe_report_export)进入最终的get_organization_report_export或finished状态。failed - 下载的导出文件包含预期的卡片/报告数据。
Failure modes
失败场景
- Export stuck in : large pipes with many cards can take minutes. Wait at least 60 seconds per poll. Retry the export trigger if still
processingafter several minutes.processing - returns
get_pipe_reportsfornull: known Pipefy API behavior; the tool omits that field automatically.cardCount - Filter rejected before GraphQL: do not pass ; use
{"current_phase":["id"]}+operator(see step 2 above).queries - Filter not working after create: use to confirm the exact
get_pipe_report_filterable_fieldsstring andfieldformat.value
- 导出卡在状态: 包含大量卡片的大型管道可能需要数分钟处理时间。每次轮询至少间隔60秒。若数分钟后仍处于
processing状态,可重新触发导出。processing - 返回的
get_pipe_reports为cardCount: 这是Pipefy API的已知行为;工具会自动省略该字段。null - 筛选条件在GraphQL执行前被拒绝: 请勿传入格式;需使用
{"current_phase":["id"]}+operator结构(参见上述步骤2)。queries - 创建后筛选条件不生效: 使用确认精确的
get_pipe_report_filterable_fields字符串和field格式。value
See also
另请参阅
- — export automation job history (different from pipe reports).
skills/observability/ - — discover
skills/introspection/input shape for complex filters.ReportCardsFilter
- — 导出自动化任务历史(与管道报告不同)。
skills/observability/ - — 为复杂筛选条件探索
skills/introspection/的输入结构。ReportCardsFilter