MCPInstall

pipefy-reports

Use this skill when the user wants to create, read, update, delete, or export pipe reports or organization reports. Covers the async export workflow (trigger, poll, download).

Installs
682
Last 24h
+10
Trending rank
#8771
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/pipefy/ai-toolkit --skill pipefy-reports
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads pipefy-reports automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Reports

Read the MCP reference or CLI reference for the surface you are using. Load only the relevant reference.

Pipe reports and organization reports: discovery, CRUD, and async exports.


Cross-cutting patterns

  • Build ReportCardsFilter using get_pipe_report_columns and get_pipe_report_filterable_fields; use introspect_type for uncommon inputs.
  • get_pipe_reports omits cardCount in the query (Pipefy can error when resolving it).

Pipe report tools

OperationRead-onlyPurpose
get_pipe_reportsYesList all reports for a pipe.
get_pipe_reportsYesLoad one report by report_id when needed.
get_pipe_report_columnsYesDiscover available columns for a report filter.
get_pipe_report_filterable_fieldsYesDiscover filterable fields for a report.
create_pipe_reportNoCreate a new pipe report.
update_pipe_reportNoUpdate report name or filters.
delete_pipe_reportNoDestructive; review and approve first. Use the selected surface's confirmation flow if one exists.
export_pipe_reportNoTrigger async export.

Organization report tools

OperationRead-onlyPurpose
get_organization_reportsYesList all org-level reports.
get_organization_reportYesSingle org report data.
create_organization_reportNoCreate an org-wide report.
update_organization_reportNoUpdate report config.
delete_organization_reportNoDestructive; review and approve first. Use the selected surface's confirmation flow if one exists.
export_organization_reportNoTrigger async export.

Export status & download

OperationPurpose
get_pipe_report_exportPoll pipe report export status (after export_pipe_report).
get_organization_report_exportPoll org report export status (after export_organization_report).
export_pipe_audit_logsExport pipe audit logs (separate from card report exports).

Steps — export a pipe report

  1. List available reports:

    Operation: get_pipe_reports pipe_uuid=<PIPE_UUID> (get_pipe supplies the UUID).

  2. Trigger the export:

    Operation: export_pipe_report pipe_id=67890 pipe_report_id=123

  3. Poll until done:

    Operation: get_pipe_report_export export_id=<EXPORT_ID>

    Repeat every 5–10 seconds until state is done (or failed).

  4. Download: use the signed fileURL from the done export response over HTTPS.

    The link expires 1 hour after the read that returned it, and anyone holding it can download the file until then. When you hand it to the user, say that it expires in 1 hour; for a fresh link, read the export again.


Steps — create a filtered pipe report

  1. Discover filterable fields:

    Operation: get_pipe_report_filterable_fields pipe_uuid=<PIPE_UUID> (get_pipe supplies the UUID).

  2. Create the report with a ReportCardsFilter shape (not a top-level current_phase array):

    Arguments:

    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 exact field string from step 1. Invalid shapes are rejected before GraphQL with a message pointing at get_pipe_report_filterable_fields.


Success criteria

  • get_pipe_report_export (or get_organization_report_export) reaches a terminal done or failed state.
  • Downloaded export contains the expected card/report data.

Failure modes

  • Export stuck in processing: large pipes with many cards can take minutes. If the export is still processing after a minute of polling every 5 to 10 seconds, poll once every 60 seconds instead. Retry the export trigger if still processing after several minutes.
  • get_pipe_reports returns null for cardCount: known Pipefy API behavior; the tool omits that field automatically.
  • Filter rejected before GraphQL: do not pass {"current_phase":["id"]}; use operator + queries (see step 2 above).
  • Filter not working after create: use get_pipe_report_filterable_fields to confirm the exact field string and value format.

See also

  • pipefy-observability — export automation job history (different from pipe reports).
  • pipefy-introspection — discover ReportCardsFilter input shape for complex filters.

FAQ

What does the pipefy-reports skill do?

Use this skill when the user wants to create, read, update, delete, or export pipe reports or organization reports. Covers the async export workflow (trigger, poll, download).

How do I install pipefy-reports?

Run npx skills add https://github.com/pipefy/ai-toolkit --skill pipefy-reports in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pipefy-reports/ (personal) or .claude/skills/pipefy-reports/ (project).

Which AI agents can use pipefy-reports?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is pipefy-reports safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains pipefy-reports?

It is published by pipefy in pipefy/ai-toolkit. It has 682 recorded installs.

More from pipefy/ai-toolkit

View all →

pipefy-observability

pipefy/ai-toolkit

Use this skill when the user wants to check AI agent logs, automation execution logs, org-level usage stats, AI credit consumption, or export automation job history.

DevOps & Cloud688 installs

pipefy-automations

pipefy/ai-toolkit

Use this skill when the user wants to create, read, update, or delete traditional automations (if/then rules) or AI automations (prompt-driven). For AI agents (conversational), see pipefy-ai-agents.

AI & Agents687 installs

pipefy-pipes-and-cards

pipefy/ai-toolkit

Use this skill when the user wants to read, create, update, or delete pipes, phases, phase fields, labels, cards, comments, or field conditions. Use the seed-pipe-across-phases workflow when populating empty phases for demos or QA.

Testing & QA685 installs

pipefy-portal-setup

pipefy/ai-toolkit

Use this skill when the user wants to list, create, or configure Pipefy portals (main hub, pages, page elements, sub-portals, publish/unpublish). Uses Interfaces and internalapi. Not for pipes/cards.

Backend & APIs684 installs

pipefy-introspection

pipefy/ai-toolkit

Use this skill when you need to discover GraphQL type shapes, mutation signatures, enum values, or execute arbitrary GraphQL as a fallback. This is the first fallback tier (Tier 2) when dedicated operations fail or don't exist for an operation.

Backend & APIs684 installs

pipefy-api-fallback

pipefy/ai-toolkit

Use this skill when a toolkit operation fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow the 3-tier resolution strategy before reaching this point.

Backend & APIs684 installs

Popular productivity & automation skills

View category →

agent-browser

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

OfficialProductivity & Automation1.3M installs

lark-doc

open.feishu.cn

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

lark-base

open.feishu.cn

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

lark-drive

open.feishu.cn

飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。

lark-shared

open.feishu.cn

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

lark-im

open.feishu.cn

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。